Skip to content

NO-ISSUE: Update to use rukpakv1alpha2 apis#108

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
kevinrizza:update-rukpak-to-v1alpha2
Feb 1, 2024
Merged

NO-ISSUE: Update to use rukpakv1alpha2 apis#108
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
kevinrizza:update-rukpak-to-v1alpha2

Conversation

@kevinrizza
Copy link
Copy Markdown
Member

Includes controller runtime bump changes

@openshift-ci openshift-ci Bot requested review from dtfranz and perdasilva January 26, 2024 19:57
Comment thread cmd/main.go
Comment on lines -82 to -83
MetricsBindAddress: metricsAddr,
Port: 9443,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Did you mean to remove these?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Yeah.

kubernetes-sigs/controller-runtime#2407

Controller runtime reimplemented the metrics server configuration, and given the state of this project I didn't think it was worth reconfiguring so I just removed the metrics configuration rather than reimplementing it. It wouldn't be a ton of effort to do, but I think we want to try to move toward getting rid of this thing entirely once we start swapping out rukpak.

Ref: image,
},
},
/*
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I would delete this

return rukpakv1alpha1.BundleDeploymentSpec{
func buildBundleDeployment(image string) rukpakv1alpha2.BundleDeploymentSpec {
return rukpakv1alpha2.BundleDeploymentSpec{
ProvisionerClassName: plainProvisionerID,
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Looks like ProvisionerClassName should be registryProvisionerID. The bundle provisioner id would go in here.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I actually think platform operators was specifically designed not to work with registryv1 bundles. Did we lose the plain provisioner in the latest revision?

Copy link
Copy Markdown

@varshaprasad96 varshaprasad96 Jan 26, 2024

Choose a reason for hiding this comment

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

Plain provisioner does exist. I noticed BundleSpec.provisionerClassName to be registry. Which is what made me think that this could be registryV1.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I tested this a little bit and you were correct. We actually don't have support for configuring the provisioner in PO and the only test examples we have support for are registryv1, so the right thing to migrate here is to use the registryv1 provisioner. I've updated accordingly.

@kevinrizza kevinrizza closed this Jan 26, 2024
@kevinrizza kevinrizza force-pushed the update-rukpak-to-v1alpha2 branch from 232052b to cf737e2 Compare January 26, 2024 20:31
@kevinrizza kevinrizza reopened this Jan 26, 2024
Includes controller runtime bump changes

Signed-off-by: kevinrizza <krizza@redhat.com>
@kevinrizza kevinrizza force-pushed the update-rukpak-to-v1alpha2 branch from e1858c5 to bb1111d Compare January 29, 2024 18:30
@ankitathomas
Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jan 29, 2024
Copy link
Copy Markdown

@varshaprasad96 varshaprasad96 left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@kevinrizza
Copy link
Copy Markdown
Member Author

/override openshift-e2e-aws

@kevinrizza
Copy link
Copy Markdown
Member Author

/approve

@kevinrizza
Copy link
Copy Markdown
Member Author

/override ci/prow/openshift-e2e-aws

@kevinrizza kevinrizza changed the title Update to use rukpakv1alpha2 apis NO-ISSUE: Update to use rukpakv1alpha2 apis Jan 29, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 29, 2024
@openshift-ci-robot
Copy link
Copy Markdown

@kevinrizza: This pull request explicitly references no jira issue.

Details

In response to this:

Includes controller runtime bump changes

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.

@kevinrizza kevinrizza added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 29, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 29, 2024

@kevinrizza: kevinrizza unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers.

Details

In response to this:

/override openshift-e2e-aws

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

openshift-ci Bot commented Jan 29, 2024

@kevinrizza: kevinrizza unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers.

Details

In response to this:

/override ci/prow/openshift-e2e-aws

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

openshift-ci Bot commented Jan 29, 2024

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: kevinrizza, varshaprasad96

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

The pull request process is described here

Details 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-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD cf737e2 and 2 for PR HEAD bb1111d in total

@ncdc
Copy link
Copy Markdown
Contributor

ncdc commented Jan 29, 2024

AWS flake
/retest

@grokspawn
Copy link
Copy Markdown

/retest

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6af37e4 and 1 for PR HEAD bb1111d in total

@kevinrizza
Copy link
Copy Markdown
Member Author

/retest

@m1kola
Copy link
Copy Markdown

m1kola commented Feb 1, 2024

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 1, 2024

@kevinrizza: all tests passed!

Full PR test history. Your PR dashboard.

Details

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

@openshift-merge-bot openshift-merge-bot Bot merged commit eebb073 into openshift:main Feb 1, 2024
@openshift-bot
Copy link
Copy Markdown

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-platform-operators-manager-container-v4.16.0-202402011710.p0.geebb073.assembly.stream for distgit ose-cluster-platform-operators-manager.
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/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.

8 participants