Bug 1956606 - probes FlowSchema manifest not included in any cluster profile
Summary: probes FlowSchema manifest not included in any cluster profile
Status: POST
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Abu Kashem
QA Contact: Ke Wang
Depends On: 1927397
Blocks: 1948703
TreeView+ depends on / blocked
Reported: 2021-05-04 04:08 UTC by W. Trevor King
Modified: 2021-05-14 14:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-apiserver-operator pull 1099 0 None open Bug 1956606: Revert "Merge pull request #1060" (Use the flow schema introduced in upstream) 2021-05-04 04:09:54 UTC

Description W. Trevor King 2021-05-04 04:08:50 UTC
Investigating 4.8.0-fc.2:

$ oc adm release extract --to manifests quay.io/openshift-release-dev/ocp-release:4.8.0-fc.2-x86_64
$ for X in manifests/*.yaml; do ENTRIES="$(yaml2json < "${X}" | jq -r '.[].metadata | select((.annotations // {}) | keys | tostring | contains("include.release.openshift.io/") | not) | .namespace + " " + .name + " " + (.annotations | tostring)')"; if test -
n "${ENTRIES}"; then echo "${X}"; echo "${ENTRIES}"; fi done
 probes null

That entry is [1], from [2].  Without the profile annotations, the CVO will never push it into the cluster.  No sense in keeping the manifest around then.  This bug can be used to land [3].

[1]: https://github.com/openshift/cluster-kube-apiserver-operator/blob/c03c9edf5fddf4e3fb1bc6d7afcd2a2284ca03d8/manifests/0000_20_kube-apiserver-operator_08_flowschema.yaml#L81-L82
[2]: https://github.com/openshift/cluster-kube-apiserver-operator/pull/1060
[3]: https://github.com/openshift/cluster-kube-apiserver-operator/pull/1099

Comment 1 Abu Kashem 2021-05-05 15:38:27 UTC
We also have a dependency on https://bugzilla.redhat.com/show_bug.cgi?id=1927397

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