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

[BUG]Openshift - cc does not delete objects it created #567

Closed
nmenant opened this issue Feb 14, 2018 · 2 comments
Closed

[BUG]Openshift - cc does not delete objects it created #567

nmenant opened this issue Feb 14, 2018 · 2 comments
Assignees
Labels

Comments

@nmenant
Copy link

nmenant commented Feb 14, 2018

Description

<For bug: Describe the bug in detail, observed versus expected behavior, steps to reproduce the issue, and a brief description of your deployment scenario>

When we use CC to handle Openshift routes, it will create all the needed objects on BIG-IP. However if we delete these routes, some objects will be deleted while some others will remain. It may be good to make sure that CC handle the whole lifecycle on any objects it creates on the BIG-IP

Example of objects that cc will not remove when a configmap / route / ab deployment is deleted:

  • if there is no more route, we would expect that the default http/https vs would be deleted
  • nodes will remain
  • the iRule to spread the traffic between two application in an ab deployment remains. Its related datagroup remains also
  • http_redirect_irule remains
  • openshift_passthrough_irule remains
  • https_redirect_dg datagroup
  • ssl_passthrough_servername_dg datagroup
  • ssl_reencrypt_servername_dg datagroup
  • ssl_reencrypt_serverssl_dg datagroup
  • Any monitors created through routes setup

Kubernetes Version

oc v3.7.0+7ed6862 kubernetes v1.7.6+a08f5eeb62

Controller Version

1.4

BIG-IP Version

12.1.1 #### Diagnostic Information Note: Sanitize the data. For example, be mindful of IPs, ports, application names and URLs Note: The following F5 article outlines the information required when opening an issue. https://support.f5.com/csp/article/K60974137

Here is an example of my /config/partitions/kubernetes/bigip.conf after deployed a confimap, routes, ab deployment and then deleted those items. It would be expected that it's empty.

bigip.conf.gz

@sjberman
Copy link
Contributor

A few notes of things I've noticed:

  • iRules and datagroups are currently long lived. They are created on startup and only have purpose if Routes (or Ingresses for redirect) have been created to use them, otherwise they are stale.
  • If multiple Routes w/ monitors are created, and one Route goes away, its monitor remains.
  • If all Routes are deleted, all resources are cleaned up (except iRules/datagroups)

@nmenant
Copy link
Author

nmenant commented Feb 15, 2018

yeah, i've tested further and that's what i've seen. I was monitoring all the namespaces by default with CC and therefore i had additional pools that got created (like for docker registry). Therefore all the monitors remained as highlighted by @sjberman .

I've changed my cc setup to only monitor my demo namespace and now everything is deleted properly with the exception of iRules Datagroups when all my routes are deleted

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

No branches or pull requests

3 participants