Bug 1819025 - Vertical pod autoscaler CRDs installed with the operator manifests are failing conditions
Summary: Vertical pod autoscaler CRDs installed with the operator manifests are failin...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Joel Smith
QA Contact: Weinan Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-31 01:08 UTC by Jessica Forrester
Modified: 2020-07-13 17:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:24:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift vertical-pod-autoscaler-operator pull 12 0 None closed Update CRD to match CRD in operand repo 2020-06-23 09:41:25 UTC
Github openshift vertical-pod-autoscaler-operator pull 13 0 None closed Bug 1819025: Update OLM manifests CRD to match CRD in operand repo 2020-06-23 09:41:24 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:24:31 UTC

Description Jessica Forrester 2020-03-31 01:08:07 UTC
Two of the CRDs included in the VPA operator's manifests are getting flagged with conditions when installed.

VerticalPodAutoscaler is getting these:

    - type: NonStructuralSchema
      status: 'True'
      lastTransitionTime: '2020-03-30T19:50:27Z'
      reason: Violations
      message: >-
        spec.validation.openAPIV3Schema.type: Required value: must not be empty
        at the root
    - type: KubernetesAPIApprovalPolicyConformant
      status: 'False'
      lastTransitionTime: '2020-03-30T19:50:27Z'
      reason: MissingAnnotation
      message: >-
        protected groups must have approval annotation
        "api-approved.kubernetes.io", see
        https://github.com/kubernetes/enhancements/pull/1111



VerticalPodAutoscalerCheckpoint is getting:

    - type: KubernetesAPIApprovalPolicyConformant
      status: 'False'
      lastTransitionTime: '2020-03-30T19:50:27Z'
      reason: MissingAnnotation
      message: >-
        protected groups must have approval annotation
        "api-approved.kubernetes.io", see
        https://github.com/kubernetes/enhancements/pull/1111

Comment 1 Joel Smith 2020-04-13 14:01:04 UTC
Regarding KubernetesAPIApprovalPolicyConformant, both VerticalPodAutoscaler and VerticalPodAutoscalerCheckpoint are upstream API groups and I wasn't readily able to find any PRs that reference API review. I'll bring it up in sig-autoscaling.

The NonStructuralSchema error should be fixed by https://github.com/openshift/vertical-pod-autoscaler-operator/pull/12

Comment 6 errata-xmlrpc 2020-07-13 17:24:11 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, 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/RHBA-2020:2409


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