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.

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

uninstallation instructions for Openshift operator #3626

Open
mikeoleary opened this issue Oct 29, 2024 · 3 comments
Open

uninstallation instructions for Openshift operator #3626

mikeoleary opened this issue Oct 29, 2024 · 3 comments

Comments

@mikeoleary
Copy link

Setup Details

Build: f5networks/k8s-bigip-ctlr:latest
Orchestration: OSCP

Description

Customer is asking for uninstallation instructions for Openshift operator. Our documentation for operator installation does not cover uninstallation.

The trigger for this question was that after uninstallation, the customer still saw references to F5 BIG-IP. For example, the JSON output of a Route object showed that .status.ingress[0].routerName was "F5 BIG-IP".

If this is a non-issue, please advise. If uninstallation of Operator is simply "click uninstall button", then please advise, thank you!

Expected Result

Uninstallation instructions included in docs

Actual Result

Uninstallation instructions are not included in docs

@mikeoleary mikeoleary added bug untriaged no JIRA created labels Oct 29, 2024
@AlainPlante
Copy link

Thanks Mike. Hopefully someone will have ran into the issue.

the route is local to openshift running in azure. No config left on the F5

@trinaths
Copy link
Contributor

trinaths commented Nov 6, 2024

Created CONTCNTR-4972 for internal tracking.

@trinaths trinaths added JIRA and removed untriaged no JIRA created labels Nov 6, 2024
@mikeoleary
Copy link
Author

@trinaths , FYI, this customer was able to just clean up the status on the Route that referred to a Router that no longer exists.

Red Hat have a solution and even a clean up script: https://access.redhat.com/solutions/5918171

So this is not high priority and is more of a clean-up issue on the Openshift side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants