Forum Discussion
F5 kubernetes f5 controller failing to compose 'poolMemberAddrs' and failing to generate F5 objects
Hello everyone,
i was able to make work of creating VS on F5 with Kubernetes 1.6.4 by setting permissive RBAC settings using this command.
kubectl create clusterrolebinding add-on-cluster-admin --clusterrole=cluster-admin --serviceaccount=kube-system:default
It can be seen at the end of this document
Edit: It is possible that it is not a complete fix. I saw some messages in syslog about the pool ip addresses. Now I see a virtual server in F5, but still no pool members. I'm using same ConfigMap that is in this thread.
Edit2: The RBAC setting did not help. If anyone has any suggestions, i'm willing to test them.
The F5 container connector doesn't support v1.6 just yet. Work is happening now to add support for this. Mainly because v1.6.x requires RBAC. So the k8s-bigip-ctlr needs to have a cluster role in order to access the API server.
I can update you as the dev team makes progress on this.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com