Bug 1504017

Summary: [RFE] IPv6 support when configuring OpenStack Kuryr as the SDN
Product: OpenShift Container Platform Reporter: Antoni Segura Puimedon <asegurap>
Component: RFEAssignee: Antoni Segura Puimedon <asegurap>
Status: CLOSED WONTFIX QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aos-bugs, jokerman, mmccomas, myllynen, tsedovic, tzumainn
Target Milestone: ---Keywords: FutureFeature, Triaged
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-11 21:40:52 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: 1503243    
Bug Blocks:    

Description Antoni Segura Puimedon 2017-10-19 10:05:54 UTC
Description of problem:

Kuryr supports IPv6 operation of OpenShift on OpenStack clusters. We should make deploying such clustser possible with OpenShift-Ansible.

In order to complete this RFE, it is necessary to:
a) Find all the places where OpenShift-Ansible assumes IPv4
b) Make the Kuryr and OpenStack resource heat templates support IPv6

Steps to Reproduce:
1. Configure OpenShift-Ansible inventory to set up a IPv6 cluster
2. ansible-playbook playbooks/byo/config.yml -vvv
3. oc run --image=celebdor/kuryr-demo demo
4. oc expose dc/demo --port 80 --targetPort 8080
5. oc get ep
6. oc get svc

Actual results:
Not implemented

Expected results:

oc get ep should return the pods IPv6 addresses for the demo service
oc get svc should show the service IPv6 VIP.
Communication should work

Comment 4 Kirsten Newcomer 2019-06-11 21:40:52 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.