Skip to content

Conversation

@timflannagan
Copy link
Contributor

See https://issues.redhat.com/browse/OCPBUGS-1456 for more information.

Adds the openshift-platform-operators system namespace and the CRDs for platform operators/rukpak to the related objects array. Ensures the Pods that get deployed by the CVO follow any openshift conventions defined as conformance tests.

Signed-off-by: timflannagan <timflannagan@gmail.com>
…ce + CRDs to related objects

Signed-off-by: timflannagan <timflannagan@gmail.com>
…as a related object

Signed-off-by: timflannagan <timflannagan@gmail.com>
Signed-off-by: timflannagan <timflannagan@gmail.com>
@openshift-ci-robot
Copy link

@timflannagan: This pull request references Jira Issue OCPBUGS-1456, which is invalid:

  • expected the bug to target the "4.12.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

See https://issues.redhat.com/browse/OCPBUGS-1456 for more information.

Adds the openshift-platform-operators system namespace and the CRDs for platform operators/rukpak to the related objects array. Ensures the Pods that get deployed by the CVO follow any openshift conventions defined as conformance tests.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 19, 2022
@timflannagan
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 19, 2022
@openshift-ci-robot
Copy link

@timflannagan: This pull request references Jira Issue OCPBUGS-1456, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.0) matches configured target version for branch (4.12.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot requested review from exdx and tylerslaton September 19, 2022 16:37
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 19, 2022
@timflannagan
Copy link
Contributor Author

/payload 4.12 nightly informing

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2022

@timflannagan: trigger 49 job(s) of type informing for the nightly release of OCP 4.12

  • periodic-ci-openshift-release-master-nightly-4.12-e2e-alibaba-ovn
  • periodic-ci-openshift-release-master-nightly-4.12-console-aws
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-csi
  • periodic-ci-openshift-release-master-ci-4.12-e2e-aws-ovn
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-ovn-fips
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-ovn-single-node
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-ovn-single-node-serial
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-sdn
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-sdn-cgroupsv2
  • periodic-ci-openshift-release-master-ci-4.12-e2e-aws-sdn-techpreview
  • periodic-ci-openshift-release-master-ci-4.12-e2e-aws-sdn-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-azure-csi
  • periodic-ci-openshift-release-master-ci-4.12-e2e-azure-ovn
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-azure-sdn
  • periodic-ci-openshift-release-master-ci-4.12-e2e-azure-sdn-techpreview
  • periodic-ci-openshift-release-master-ci-4.12-e2e-azure-sdn-techpreview-serial
  • periodic-ci-openshift-release-master-ci-4.12-e2e-azure-upgrade-ovn-single-node
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-azure-deploy-cnv
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-azure-upgrade-cnv
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-driver-toolkit
  • periodic-ci-openshift-release-master-ci-4.12-e2e-gcp-ovn
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-gcp-ovn-csi
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-gcp-ovn-rt
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-gcp-sdn
  • periodic-ci-openshift-release-master-ci-4.12-e2e-gcp-sdn-techpreview
  • periodic-ci-openshift-release-master-ci-4.12-e2e-gcp-sdn-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.12-upgrade-from-stable-4.11-e2e-metal-ipi-bm-upgrade
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-ovn-dualstack
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-sdn-bm-upgrade
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-sdn-serial-ipv4
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-sdn-serial-virtualmedia
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-serial-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-serial-ovn-dualstack
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ipi-upgrade-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.12-upgrade-from-stable-4.11-e2e-metal-ipi-upgrade-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-sdn-assisted
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-ovirt-csi
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-ovirt-sdn
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-ovn-proxy
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-metal-ovn-single-node-live-iso
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-sdn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.12-upgrade-from-stable-4.11-e2e-aws-sdn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-vsphere-ovn-csi
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-vsphere-ovn-serial
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-vsphere-ovn-techpreview
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-vsphere-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-vsphere-ovn-upi
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-vsphere-ovn-upi-serial
  • periodic-ci-openshift-release-master-nightly-4.12-e2e-vsphere-sdn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f0d5d3f0-3839-11ed-8e0c-d58ae1444121-0

Comment on lines -63 to -65
limits:
cpu: 500m
memory: 128Mi
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: we have conformance tests that verify component pods don't specify limits, and don't get assigned the BestEffort quality of service. Removing the limits resulted in the Burstable QoS being assigned to these pods.

runAsNonRoot: true
seccompProfile:
type: RuntimeDefault
priorityClassName: "system-cluster-critical"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: just mirroring what's defined for OLM sub-components here.

Comment on lines +23 to +26
resources:
requests:
cpu: 1m
memory: 15Mi
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: these requests are for the kube-rbac-proxy sidecar container. I modeled these after what cluster monitoring have defined for their deployments that utilize kube-rbac-proxy.

Comment on lines +73 to +76
resources:
requests:
cpu: 15m
memory: 100Mi
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is for the core rukpak deployment. I increased the memory request to 100Mi just because we're caching bundle contents in-memory, so we may want to invest in benchmarking this behavior to get a better read on what kind of requests we need to be setting for subsequent phases.

Comment on lines +17 to +22
- group: core.rukpak.io
name: ""
resource: bundles
- group: core.rukpak.io
name: ""
resource: bundledeployments
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prior to GA, I think we should separate out the rukpak stuff from the PO stuff. At the end of the day, PO will depend on rukpak, not provide it.

But this is fine in the mean time.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup +1.

Copy link
Member

@joelanford joelanford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 19, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joelanford, timflannagan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [joelanford,timflannagan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@joelanford
Copy link
Member

/lgtm

@openshift-merge-robot openshift-merge-robot merged commit 4ecea42 into openshift:main Sep 19, 2022
@openshift-ci-robot
Copy link

@timflannagan: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-1456 has been moved to the MODIFIED state.

In response to this:

See https://issues.redhat.com/browse/OCPBUGS-1456 for more information.

Adds the openshift-platform-operators system namespace and the CRDs for platform operators/rukpak to the related objects array. Ensures the Pods that get deployed by the CVO follow any openshift conventions defined as conformance tests.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@timflannagan timflannagan deleted the OCPBUGS-1456 branch September 19, 2022 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants