Comments (7)
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from api.
So, since I did not receive any updates on this, my assumption is that this is either a bug with low priority, or it is expected behaviour.
I investigated how this is supposed to work (looking at k8s code) and how it is implemented within OpenShift.
Without help I cannot proceed investigation and/or propose fixes.
I can only update my issue with my personal fixes as into how I implemented it.
- Namespaces are automatically cleaned, no surprises there
- ArgoCD objects, RoleBindings and Secrets reside within the namespace and are cleaned together with the namespaces. I have not put any efforts into investigating wether this is also cleaned without cleaning the namespace itself.
- OpenShift objects (Quota, users, groups,
- Other items are within objects (such as items in ArgoCD AppSet listgenerators, and lines in ConfigMap Data) and are managed by custom finaliser code of our operator
from api.
For the OpenShift objects (item 3) I have currently implemented the following custom code:
- controller detects that is being removed and runs generic finalize code
- finalize code runs specific finalize codes for specific items (item 3 and 4, Quota, groups, users, and stuff in resources)
- finalize code for groups deducts which groups where created by our operator (from main resource body) and removes as required. SImilar for other openshift stuff.
I would have loved it to be taken care of out of the box.
That would saved time and be less error prone, but we now have something that works for us.
I hope that this helps anyone else that might run into this.
If any questions, or an ambition to actually fix this, just ping us with comments in this issue.
from api.
Decided to leave this issue stale. Auto-close when rotten is fine...
from api.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
/remove-lifecycle stale
from api.
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
from api.
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen
.
Mark the issue as fresh by commenting/remove-lifecycle rotten
.
Exclude this issue from closing again by commenting/lifecycle frozen
./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from api.
Related Issues (20)
- Depends on github.com/gogo/protobuf v1.3.2 HOT 4
- Reference to the pod label "deploymentconfig" created by DeploymentConfig HOT 1
- Incorrect validation of hostname type in IngressController.operator.openshift.io/v1 HOT 4
- 'make generate-with-container' is broken with latest master HOT 1
- 'make update-codegen-crds' generates a diff with latest master HOT 4
- ImageContentPolicy Schema does not allow many valid hostnames for mirrors or sources HOT 4
- AllowPrivilegeEscalation field not exported for SecurityContextConstraints HOT 4
- 'generate' is not an supported value of mappingMethod HOT 6
- CRDs of historical Openshift resources (Route, ImageStream) for interop with envtest / operator-sdk HOT 4
- AWS load balancer annotations aren't supported HOT 4
- tools makefile version checks output git errors when vendored in another repo HOT 11
- Dependbot raised a PR to upgrade this dep to `v3.9.0+incompatible` but I don't see a tag with this name HOT 5
- パンダちゃん大嫌い HOT 2
- Start on HOT 2
- v3.9.0 tag is available on the official Go proxy but not on this repository HOT 7
- Inclusion of the CustomResourceDefinition type HOT 3
- How to replace the retracted github.com/openshift/api v3.9.0+incompatible dependency HOT 4
- Add listType tag to APIs owned by the build-api team HOT 5
- Add support for `BindOptions` in `IngressController.operator.openshift.io/v1` HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from api.