Closed xueshanf closed 1 year ago
Looking into this.
i dont see the same issue.
Please use my CRDs at https://github.com/mdditt2000/kubernetes-1-19/tree/master/cis%202.8/github/2286/split/working
Please use CIS test image located here https://github.com/mdditt2000/kubernetes-1-19/blob/master/cis%202.8/github/2286/f5-bigip-ctlr-deployment.yaml
This should work fine!!
@mdditt2000
Compared with your dashboard CRD, I found a syntax error in my pools definition, , although it's not reported in the deployment:
- path: /
service: kubernetes-dashboard-proxy
servicePort: 3000
The dash in path is causing propertyName generation error, I think. path should be at the same level with monitor. Removing the leading dash AND using the new image 2.8.0 works!
I retested cis 2.7.1, it works too! Should I stay on 2.8.0 (not released yet), or revert to 2.7.1?
Thanks! Great help!
@xueshanf do you have 30 min to chat? I am based in San Jose CA. Would like to understand your use-case and chat about 2.7x verse 2.8
Recommend validate with the latest CIS release.
Setup Details
CIS Version : 2.7.1
Build: f5networks/k8s-bigip-ctlr:latest
BIGIP Version: Big IP x.x.x
AS3 Version:
Agent Mode: AS3/CCCL
Orchestration: K8S/OSCP
Orchestration Version:
Pool Mode: Nodeport
Additional Setup details: <Platform/CNI Plugins/ cluster nodes/ etc>
CIS commandline arguments:
Description
I am trying to use CIS CRD to create kubernetets dashboard. I think it was working on CIS 2.3.x, but when I upgraded to 2.7.1, it stoped working with 422 declarationFullId error.
Steps To Reproduce
Expected Result
The virtualserver, and pools should be created on BigIP.
Actual Result
The virtual server and pool are not created due to 422 error.
Partial error logs:
Diagnostic Information
It doesn't matter if I use virtualServerName: k8s-dashboard or not, the controller seems generate a name _0_kubernetes_dashboard that is not in any of the kubernetes VirtualServer configuration spec.
Error logs:
The VS seems and TLSProfile are created alright:
Observations (if any)
See the partial controller logs. Not sure if gtm has anything to do with it - we are using LTM, not GTM.