Bug 1888861 - need to pass dual-stack service CIDRs to kube-apiserver in dual-stack cluster
Summary: need to pass dual-stack service CIDRs to kube-apiserver in dual-stack cluster
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.7.0
Assignee: Dan Winship
QA Contact: Ke Wang
URL:
Whiteboard:
Depends On:
Blocks: 1888862
TreeView+ depends on / blocked
 
Reported: 2020-10-16 00:53 UTC by Dan Winship
Modified: 2021-02-24 15:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1888862 (view as bug list)
Environment:
Last Closed: 2021-02-24 15:26:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-apiserver-operator pull 986 0 None closed Bug 1888861: set servicesSubnet correctly in dual-stack clusters 2020-12-21 08:44:31 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:26:53 UTC

Description Dan Winship 2020-10-16 00:53:00 UTC
Description of problem:
We had not yet updated cluster-kube-apiserver-operator to pass both service CIDRs to kube-apiserver when the cluster was dual-stack

Steps to Reproduce:
1. Deploy dual-stack cluster
2. Try to create a service with `ipFamily: IPv6`

Actual results:
error

Expected results:
an IPv6 service

Comment 2 Dan Winship 2020-10-26 16:55:57 UTC
I can verify this:

# oc rsh -n openshift-kube-apiserver kube-apiserver-master-0
sh-4.4# jq . < /etc/kubernetes/static-pod-resources/configmaps/config/config.yaml | grep servicesSubnet
  "servicesSubnet": "172.30.0.0/16,fd02::/112",

Comment 5 errata-xmlrpc 2021-02-24 15:26:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:5633


Note You need to log in before you can comment on or make changes to this bug.