openstack-k8s-operators dependency bump branch: main#2
Open
github-actions[bot] wants to merge 1 commit into
Open
openstack-k8s-operators dependency bump branch: main#2github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
openstack-dependency-bump/main
branch
from
d66922c to
14c9fd4
Compare
github-actions
Bot
force-pushed
the
openstack-dependency-bump/main
branch
from
14c9fd4 to
29cec19
Compare
stuggi
added a commit
that referenced
this pull request
Mar 4, 2026
Resolves compatibility topic #2 (Full Namespace Backup vs Selective Backup). Changes: 1. Backup strategy: Full namespace backup with smart exclusions - Backup ALL Secrets, ConfigMaps, CRs (complete snapshot) - Exclude operator-managed resources: pods, replicasets, jobs, events, statefulsets - PVCs filtered by openstack.org/backup: "true" label 2. Restore strategy: Selective by webhook labels - Only restore resources with openstack.org/backup-restore: "true" - Webhook labels user-provided resources (no ownerReferences) - Operator-managed resources excluded (recreated by operators) 3. Added detailed restore strategy explanation showing: - User-provided Secrets → Labeled → Restored - Operator-created Secrets → Not labeled → Recreated - Same logic for ConfigMaps and other resources 4. Updated Goals section to emphasize "Full Backup, Selective Restore" Decision: Backup everything (complete snapshot), restore selectively (webhook labels). This matches current Ansible approach but with automatic filtering via webhooks. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
stuggi
added a commit
that referenced
this pull request
Mar 13, 2026
Resolves compatibility topic #2 (Full Namespace Backup vs Selective Backup). Changes: 1. Backup strategy: Full namespace backup with smart exclusions - Backup ALL Secrets, ConfigMaps, CRs (complete snapshot) - Exclude operator-managed resources: pods, replicasets, jobs, events, statefulsets - PVCs filtered by openstack.org/backup: "true" label 2. Restore strategy: Selective by webhook labels - Only restore resources with openstack.org/backup-restore: "true" - Webhook labels user-provided resources (no ownerReferences) - Operator-managed resources excluded (recreated by operators) 3. Added detailed restore strategy explanation showing: - User-provided Secrets → Labeled → Restored - Operator-created Secrets → Not labeled → Recreated - Same logic for ConfigMaps and other resources 4. Updated Goals section to emphasize "Full Backup, Selective Restore" Decision: Backup everything (complete snapshot), restore selectively (webhook labels). This matches current Ansible approach but with automatic filtering via webhooks. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
stuggi
added a commit
that referenced
this pull request
Mar 18, 2026
Resolves compatibility topic #2 (Full Namespace Backup vs Selective Backup). Changes: 1. Backup strategy: Full namespace backup with smart exclusions - Backup ALL Secrets, ConfigMaps, CRs (complete snapshot) - Exclude operator-managed resources: pods, replicasets, jobs, events, statefulsets - PVCs filtered by openstack.org/backup: "true" label 2. Restore strategy: Selective by webhook labels - Only restore resources with openstack.org/backup-restore: "true" - Webhook labels user-provided resources (no ownerReferences) - Operator-managed resources excluded (recreated by operators) 3. Added detailed restore strategy explanation showing: - User-provided Secrets → Labeled → Restored - Operator-created Secrets → Not labeled → Recreated - Same logic for ConfigMaps and other resources 4. Updated Goals section to emphasize "Full Backup, Selective Restore" Decision: Backup everything (complete snapshot), restore selectively (webhook labels). This matches current Ansible approach but with automatic filtering via webhooks. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated changes by create-pull-request GitHub action