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
Shared Pool not working with v2 #2151
Comments
@rgarcia89 validated with the following configuration that the nodes are getting created in /Common using sharednodes = true in the declaration. This is what is expected from CIS 2.6.1 Here is my repo - https://github.com/mdditt2000/kubernetes-1-19/tree/master/cis%202.7/github/2151 |
Hi @mdditt2000 I think you picked the wrong ticket? Your answer seems more to be about #2101 |
@rgarcia89 understand you using a reference to shared pool which most likely CIS doesn't understand. I will look into that tomorrow. Can we chat tomorrow? I want to understand what you trying to achieve. Please email me at m.dittmer@f5.com BTW checkout this new features coming in CIS 2.7. Its shared-pools etc but even better https://github.com/mdditt2000/kubernetes-1-19/blob/master/cis%202.7/tenant-configmap/README.md |
Of course I will send you an email to arrange a slot to chat. |
@rgarcia89 where you able to resolve this issue with Kostas? |
Not yet unfortunately. He wanted to come back to me |
Will reach out to Kostas. Thanks! |
Please find the steps to replicate the issue:
you should see a service (namespace: monitoring) alertmanager-operated ClusterIP None 9093/TCP,9094/TCP,9094/UDP 11h edit the service and add the labels shared by Raul
you should see the error mentioned by Raul |
Created [CONTCNTR-3158] for internal tracking. |
@rgarcia89 @skenderidis @trinaths please note the following works fine
My changes
@rgarcia89 please try my configmap. Change your ports back. |
@mdditt2000 I do not see any changes other than your mentioned removes, which need to be defined on my side. |
Investigation in the next sprint starting this week. |
@rgarcia89 , we have identified the root cause of the issue. It's happening because service "alertmanager-operated" in namespace "monitoring" is using the same port no for TCP & UDP protocol. And CIS is adding the duplicate pool members for both of these endpoints, which is rejected by the AS3 JSON schema.
Would it be possible for you to use the different TCP & UDP port no in this service? |
Hi @vklohiya these ports are coming from the Prometheus operator / helm chart and are unfortunately not configurable 😕 |
@vklohiya also just to make you aware. This works totally fine in version |
Thanks for the update @rgarcia89 , we are working on it. |
@skenderidis @vklohiya @mdditt2000 same issue with v2.8.1 |
Created CONTCNTR-3253 to fix this issue. ETA 2.9 |
Hi all,
As soon as we remove one port from the service, everything gets created. That's why it was working for @mdditt2000 as stated here |
@sebidude , Let me check it and get back to you. |
@sebidude , it's working fine with following service definition in CIS 2.9.0:
Could you share the reproduction steps and your configMap configuration along with service? |
Hey @vklohiya Here is the service:
And here is the configmap that contains the corresponding as3 declaration:
|
@sebidude , CIS is deployed in ClusterIP mode or NodePort mode? |
NodePort mode. |
@vklohiya we ran it in the debugger and noticed, that the fix which was merged with #2396 does not handle duplicate pool members when the controller is deployed in NodePort mode. we just added } else { // Controller is in NodePort mode.
if service.Spec.Type == v1.ServiceTypeNodePort {
for _, port := range service.Spec.Ports {
endpointMembers := appMgr.getEndpointsForNodePort(port.NodePort, port.Port)
for _, newMember := range endpointMembers {
if _, ok := uniqueMembersMap[newMember]; !ok {
uniqueMembersMap[newMember] = struct{}{}
members = append(members, newMember)
}
}
}
}
} and made it working. Please verify and release a bugfix as soon as possible. Cheers |
@sebidude , thanks for identifying the fix. Can you please raise a separate github issue to track this? |
Setup Details
CIS Version : 2.6.1
Build: f5networks/k8s-bigip-ctlr:latest
BIGIP Version: BIG-IP v16.1.1 (Build 0.0.16)
AS3 Version: 3.31.0
Agent Mode: AS3
Orchestration: K8S
Orchestration Version: 1.20.14
Pool Mode: Nodeport
Additional Setup details: CentOS 7.9
Description
When trying deploy a shared pool, controller v2 seems to run into an issue, even having the service port number defined correctly.
The issue appears as followed in the logs:
Steps To Reproduce
Expected Result
Two virtual servers should be created with a shared pool
Actual Result
CIS runs into an issue
Diagnostic Information
Observations (if any)
The text was updated successfully, but these errors were encountered: