-
Notifications
You must be signed in to change notification settings - Fork 21
ESO-424:Added e2e test cases from openshift test private. #160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
siddhibhor-56
wants to merge
2
commits into
openshift:main
Choose a base branch
from
siddhibhor-56:more-e2es
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: openshift/external-secrets-operator
Length of output: 5754
🏁 Script executed:
Repository: openshift/external-secrets-operator
Length of output: 3179
🏁 Script executed:
Repository: openshift/external-secrets-operator
Length of output: 4188
🌐 Web query:
Kubernetes NamespaceStatus phase Terminating deletionTimestamp before phase changes namespace deletion semantics💡 Result:
In Kubernetes, the interaction between the
Namespace.Status.Phaseand themetadata.deletionTimestampis a core mechanism of the graceful deletion process [1][2]. When aDELETErequest is issued for a namespace, the API server sets themetadata.deletionTimestampto the current server time [1][3]. This timestamp acts as the primary indicator that a graceful deletion has been requested [3][4]. Upon observing this change, thenamespace-controllerupdates theNamespace.Status.PhasefromActivetoTerminating[1][5]. The deletion process follows these semantics: 1. Request and Marking: The presence of a non-nildeletionTimestampprevents the creation of new objects within the namespace [6]. The phase transition toTerminatingsignals to users and system components that the namespace is undergoing cleanup and is no longer available for new workloads [7][8]. 2. Resource Cleanup: Thenamespace-controllerbegins iterating through and deleting all content (resources) associated with the namespace [1][6]. 3. Finalization: The namespace itself contains aspec.finalizerslist (typically including thekubernetesfinalizer) [1][2]. The namespace cannot be removed from storage until this list is empty [3][4]. Thenamespace-controlleris responsible for purging the namespace's contents and, upon successful cleanup, removing the finalizers [1][6]. 4. Permanent Removal: Once all finalizers are removed and thedeletionTimestampis set, thenamespace-controllersends a finalDELETEaction to the API server to permanently remove the namespace object from etcd storage [1][2]. If a namespace remains stuck in theTerminatingphase, it is typically because one or more finalizers have not been removed, often due to a controller failing to successfully clean up the associated resources or a manual error (e.g., specifying a non-existent finalizer) [9][3][8]. Because thedeletionTimestampis already set, the namespace is effectively "locked" into the deletion flow until the finalizers are cleared [3][4]. Top results: [1][5][6][9][3]Citations:
Treat a non-nil
deletionTimestampas terminating. Lines 75-76 can return while the namespace is already marked for deletion but still reportsActive, letting setup continue before teardown finishes and making later readiness checks flaky.🤖 Prompt for AI Agents