Bug 1579376

Summary:	[RFE] Support optional Kuryr controller highly available deployments
Product:	OpenShift Container Platform	Reporter:	Antoni Segura Puimedon <asegurap>
Component:	RFE	Assignee:	Michał Dulko <mdulko>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	aos-bugs, jokerman, mmccomas, scuppett
Target Milestone:	---	Keywords:	Reopened
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-12 11:54:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1579371
Bug Blocks:

Description Antoni Segura Puimedon 2018-05-17 13:36:54 UTC

Description of problem:
When Kuryr is deployed as OpenShift's SDN, its deployment consists in just one Pod.

This RFE is about supporting specifying a desired amount of replicas for the Deployment once the kuryr controller supports HA.


Steps to Reproduce:
1. The user should specify a group variable like openshift_openstack_kuryr_controller_replicas: 3
2. Deploy the cluster
3. oc -n openshift-infra get po -o yaml
4. Check which is the master
5. oc -n openshift-infra delete po name of the master controller
6. Create a deploymentconfig and a service

Actual results:
The controllers would compete and add unhealthy load to Neutron

Expected results:
Each event only gets processed by a single Controller.
Check that the new deploymentconfig and service gets connectivity and that another controller pod took leadership.

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 1 Antoni Segura Puimedon 2018-11-12 16:56:44 UTC


*** This bug has been marked as a duplicate of bug 1579371 ***

Comment 3 Kirsten Newcomer 2019-06-12 11:54:50 UTC

With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.