-
## Story
As a ***devops engineer***,
I would like to ***use a better supported terraform provider for cloudfoundry***,
So that I can ***be confident that everything works properly and will contin…
-
### Describe the problem
We strive for declarative catalog, therefore orphan resources should be cleaned up once they are orphaned from the repository.
### Steps to reproduce the problem
1. Remove …
-
#### Describe the issue
vault-agent configmap is not deleted when pod is gone. This becomes an issue when having hundreds of thousands of these orphaned resources in the cluster which can happen qu…
-
### What problem are you facing?
When a provider is deleted it deletes all the managed resources. Even though it makes sense from a hierarchical perspective, it can be seriously dangerous in produc…
-
I notice in platform-test that there are some orphaned PR environments for closed PRs. I don't know if this is the right solution for this issue, but we could add a check for PR environments that map …
-
If the master process is not running when a node is deleted, it will miss the event. There will then be orphaned resources, e.g. router ports.
This can be fixed in two ways - either by adding ovn-k…
-
If namespaced resources exist, but their associated namespace does not, the namespace lifecycle controller does not recognize/remedy this.
-
### Proposed change
It would be useful for there to be a mechanism to locate all resources or possibly orphaned spawners and stop them.
There are 3 main sources of these orphans:
1. plain old…
-
When leaf node found an orphaned block, the block entered the queue, but master block won't accept the orphaned block as the hash doesn't exist in the master blockchain database. This causing master n…
-
# Summary
Instead of shoehorning orphaned into the normal applications, I think I'd like to see synthetic apps - one per namespace that list all unaccounted-for resources.
# Motivation
If you…