Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-33750: Bump version of DNSNameResolver controller #415

Merged

Conversation

arkadeepsen
Copy link
Member

@arkadeepsen arkadeepsen commented Jun 5, 2024

This PR bumps the version of the the DNSNameResolver controller. This PR also adds the additional RBAC permissions required by the CoreDNS pods for the DNSNameResolver CRs.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 5, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jun 5, 2024
@openshift-ci-robot
Copy link
Contributor

@arkadeepsen: This pull request references Jira Issue OCPBUGS-33750, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @huiran0826

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

In response to this:

This PR bumps the version of the the DNSNameResolver controller.

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.

@arkadeepsen
Copy link
Member Author

Depends on openshift/coredns-ocp-dnsnameresolver#8

@arkadeepsen arkadeepsen force-pushed the dnsnameresolver-controller branch from bc00361 to 05c8a76 Compare July 12, 2024 10:18
@arkadeepsen arkadeepsen changed the title [WIP] OCPBUGS-33750: Bump version of DNSNameResolver controller OCPBUGS-33750: Bump version of DNSNameResolver controller Jul 12, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 12, 2024
@arkadeepsen
Copy link
Member Author

/test ?

Copy link
Contributor

openshift-ci bot commented Jul 12, 2024

@arkadeepsen: The following commands are available to trigger required jobs:

  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-operator
  • /test e2e-aws-ovn-serial
  • /test e2e-aws-ovn-upgrade
  • /test images
  • /test unit
  • /test verify

The following commands are available to trigger optional jobs:

  • /test e2e-aws-ovn-single-node
  • /test e2e-aws-ovn-techpreview
  • /test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-cluster-dns-operator-master-e2e-aws-ovn
  • pull-ci-openshift-cluster-dns-operator-master-e2e-aws-ovn-operator
  • pull-ci-openshift-cluster-dns-operator-master-e2e-aws-ovn-serial
  • pull-ci-openshift-cluster-dns-operator-master-e2e-aws-ovn-single-node
  • pull-ci-openshift-cluster-dns-operator-master-e2e-aws-ovn-techpreview
  • pull-ci-openshift-cluster-dns-operator-master-e2e-aws-ovn-upgrade
  • pull-ci-openshift-cluster-dns-operator-master-images
  • pull-ci-openshift-cluster-dns-operator-master-unit
  • pull-ci-openshift-cluster-dns-operator-master-verify

In response to this:

/test ?

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.

@arkadeepsen
Copy link
Member Author

/assign @alebedev87

@arkadeepsen
Copy link
Member Author

For ci/prow/e2e-aws-ovn-techpreview the failure is unrelated to the changes made in the PR. The specific e2e test added for DNSNameResolver has passed.
: [sig-network][OCPFeatureGate:DNSNameResolver][Feature:EgressFirewall] when using openshift ovn-kubernetes should ensure egressfirewall with wildcard dns rules is created [Suite:openshift/conformance/parallel] 27s

@alebedev87
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2024
@alebedev87
Copy link
Contributor

/lgtm cancel

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2024
Copy link
Contributor

@alebedev87 alebedev87 left a comment

Choose a reason for hiding this comment

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

Sorry for the previous review, forgot about this question.

})
cr.Rules = append(cr.Rules, rbacv1.PolicyRule{
APIGroups: []string{"network.openshift.io"},
Resources: []string{"dnsnameresolvers/status"},
Verbs: []string{"update"},
Verbs: []string{"get", "update", "patch"},
Copy link
Contributor

Choose a reason for hiding this comment

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

So this is the update related to the new get we do in the plugin. However I'm wondering whether the patch verb comes from.

Copy link
Member Author

@arkadeepsen arkadeepsen Jul 22, 2024

Choose a reason for hiding this comment

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

It was during the implementation phase when you had suggested to add get, update and patch verbs for the status subresource based on kubebuilder's suggestion. That's why I added patch as well in the list.

@alebedev87
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2024
@arkadeepsen
Copy link
Member Author

/test e2e-aws-ovn-techpreview

@alebedev87
Copy link
Contributor

/approve

Copy link
Contributor

openshift-ci bot commented Jul 24, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 24, 2024
Copy link
Contributor

openshift-ci bot commented Jul 24, 2024

@arkadeepsen: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 54eea5b into openshift:master Jul 24, 2024
10 checks passed
@openshift-ci-robot
Copy link
Contributor

@arkadeepsen: Jira Issue OCPBUGS-33750: All pull requests linked via external trackers have merged:

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

In response to this:

This PR bumps the version of the the DNSNameResolver controller. This PR also adds the additional RBAC permissions required by the CoreDNS pods for the DNSNameResolver CRs.

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-dns-operator
This PR has been included in build ose-cluster-dns-operator-container-v4.17.0-202407241715.p0.g54eea5b.assembly.stream.el9.
All builds following this will include this PR.

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. jira/severity-important Referenced Jira bug's severity is important 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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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