Closed dsullivarh closed 7 months ago
@dsullivarh Please share service and deployment manifests to validate this issue.
Were all the resources in the same namespace CIS is monitoring ?
All the route resources were in the same namespace cis was monitoring
oc get svc isam-wrp-low -o yaml apiVersion: v1 kind: Service metadata: name: xxxx-wrp-low namespace: cool-project spec: clusterIP: XX.XX.XX.XX clusterIPs:
Are you asking for the deployment of the app, we use statefulset but that shouldn't matter we don't see anything going into the f5 with what we have and we don't see any errors in the big ip controller pod
@dsullivarh we scheduling a meeting for next week. Have a great weekend.
Created [CONTCNTR-3889] for internal tracking.
Fixed with PR : https://github.com/F5Networks/k8s-bigip-ctlr/pull/2833 Closing this issue.
Setup Details
CIS Version : 2.12.0
Build: f5networks/k8s-bigip-ctlr:latest f5networks/cntr-ingress-svcs:
BIGIP Version: Big IP x.x.x
14.1.4.6 AS3 Version: 3.x
Agent Mode: AS3/CCCL default is as3
Orchestration: K8S/OSCP OSCP
Orchestration Version: OSCP 4.12.5
Pool Mode: Cluster/Nodeport Cluster
Additional Setup details: <Platform/CNI Plugins/ cluster nodes/ etc> OVNK Kuberenetes
Description
We don't see any route configuration being added following documentation from [0]
It would be nice to see a working configuration with the versions specified above.
[0] https://github.com/mdditt2000/k8s-bigip-ctlr/tree/main/user_guides/ovn-kubernetes-ha#readme
Steps To Reproduce
See above...
route configuration
Expected Result
No errors in logs we see it talking successfully to f5
But we never see any as3 route post happing
Actual Result
oc logs k8s-bigip-ctlr-01-deployment-6ff6dd75cb-s9mnl | grep -i "as3" 2023/03/15 21:32:59 [DEBUG] [AS3] No certs appended, using only system certs 2023/03/15 21:32:59 [DEBUG] [AS3] posting GET BIGIP AS3 Version request on https://XX.XXX.XX.XX/mgmt/shared/appsvcs/info 2023/03/15 21:33:02 [DEBUG] [AS3] BIGIP is serving with AS3 version: 3.43
oc logs k8s-bigip-ctlr-01-deployment-6ff6dd75cb-s9mnl | grep "Finished syncing" 2023/03/15 21:33:03 [DEBUG] Finished syncing local extended spec configmap: kube-system/global-cm (37.671µs) 2023/03/15 21:33:03 [DEBUG] Finished syncing RouteGroup/Namespace cool-project (118.18µs)
Diagnostic Information
See above
We never see any as3 post information four routing, but you do see it doing a get for as3 version
Observations (if any)
policyCR seems to be a required field although documentations says optional