Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Go examples - cleanup does not remove namespace #6791

Open
m-szalik opened this issue Jul 26, 2024 · 2 comments
Open

Go examples - cleanup does not remove namespace #6791

m-szalik opened this issue Jul 26, 2024 · 2 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@m-szalik
Copy link

After the test - cleanup - should remove the namespace.

operator-sdk/testdata/go/v4/memcached-operator/test/e2e/e2e_test.go

Line 87 in e95abdb

cmd := exec.Command("kubectl", "create", "ns", namespace)

@m-szalik m-szalik added the kind/documentation Categorizes issue or PR as related to documentation. label Jul 26, 2024
m-szalik added a commit to m-szalik/operator-sdk that referenced this issue Jul 26, 2024
@m-szalik
Cleanup aftert test should remove namespace (operator-framework#6791)
57563b6
m-szalik added a commit to m-szalik/operator-sdk that referenced this issue Jul 26, 2024
@m-szalik
Cleanup aftert test should remove namespace (operator-framework#6791)
f914011
m-szalik added a commit to m-szalik/operator-sdk that referenced this issue Jul 26, 2024
@m-szalik
Cleanup aftert test should remove namespace (operator-framework#6791)
8d954b6 
Signed-off-by: m-szalik <[email protected]>
@openshift-bot
Copy link

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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 25, 2024
@openshift-bot
Copy link

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

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@openshift-bot @m-szalik