[k8s-service-R5.0]: External floating IP object not created from floating IP pool when external IP is mentioned in k8s service
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
Fix Released
|
Critical
|
Prasanna Mucharikar | |||
Trunk |
Fix Released
|
Critical
|
Prasanna Mucharikar |
Bug Description
BUG Tempelate:
Configuration:
K8s 1.9.2
contrail-5.0-10
Centos-7.4
Setup:
5 node setup.
3 Kube master. 3 Controller.
2 Agent+ K8s slaves
Description:
Kubemaster configuration:
[VNC]
public_
On Contrail, created a VN with public IP anmed "__public__" and subnet "10.204.
Also configured a floating IP pool as "__fip_
Created a service and mentioned external IP using 1 of the IP from configured subnet :
clusterIP: 10.100.6.5
externalIPs:
- 10.204.221.164
ports:
- port: 80
protocol: TCP
targetPort: 80
selector:
app: http_test
sessionAffinity: None
type: ClusterIP
status:
loadBalancer: {}
~
Expected that floating IP will get generated in contrail and the service will be accessible from web.
Observation was that Floating IP with "10.204.221.164" did not get generated.
Thus, service wasn't accessible from outside.
Review in progress for https:/ /review. opencontrail. org/41840
Submitter: Prasanna Mucharikar (<email address hidden>)