You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<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.
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)
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
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:
Kubernetes Version
oc v3.7.0+7ed6862 kubernetes v1.7.6+a08f5eeb62Controller Version
1.4BIG-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/K60974137Here 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
The text was updated successfully, but these errors were encountered: