OCPBUGS-31257: Exclude additional files in default aide conf

[Vincent056]

We are going to exlucde following in the default aide conf:
!/hostroot/etc/cni/multus/certs for the OVN-Kubernetes CNI
!/hostroot/etc/kubernetes/compliance-operator for the Compliance Operator check runtime kubeletconfig !/hostroot/etc/kubernetes/node-feature-discovery for the Node Feature Discovery Operator

https://issues.redhat.com/browse/OCPBUGS-31257

[openshift-ci-robot]

@Vincent056: This pull request references Jira Issue OCPBUGS-31257, which is invalid:

• expected the bug to target the "4.17.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:

We are going to exlucde following in the default aide conf:
!/hostroot/etc/cni/multus/certs for the OVN-Kubernetes CNI
!/hostroot/etc/kubernetes/compliance-operator for the Compliance Operator check runtime kubeletconfig !/hostroot/etc/kubernetes/node-feature-discovery for the Node Feature Discovery Operator

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@Vincent056: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[rhmdnd]

/lgtm

Seems reasonable and existing e2e tests will verify the config works with AIDE.

It would be nice to have a separate set of situational tests that exercise the excluded config with the necessary operator, but that's a larger lift than what I think these e2e tests were intended for.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhmdnd, Vincent056

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 [Vincent056,rhmdnd]

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

[rhmdnd]

/jira refresh

[openshift-ci-robot]

@rhmdnd: This pull request references Jira Issue OCPBUGS-31257, 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.17.0) matches configured target version for branch (4.17.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @xiaojiey

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@Vincent056: Jira Issue OCPBUGS-31257: All pull requests linked via external trackers have merged:

• openshift/file-integrity-operator#534

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

In response to this:

We are going to exlucde following in the default aide conf:
!/hostroot/etc/cni/multus/certs for the OVN-Kubernetes CNI
!/hostroot/etc/kubernetes/compliance-operator for the Compliance Operator check runtime kubeletconfig !/hostroot/etc/kubernetes/node-feature-discovery for the Node Feature Discovery Operator

https://issues.redhat.com/browse/OCPBUGS-31257

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 openshift-eng/jira-lifecycle-plugin repository.