-
Notifications
You must be signed in to change notification settings - Fork 136
Bug 1948714: IBM Cloud manifest profile patch #643
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
Bug 1948714: IBM Cloud manifest profile patch #643
Conversation
|
/hold |
|
@csrwng: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
hack/update-profile-manifests.sh
Outdated
| @@ -0,0 +1,80 @@ | |||
| #!/usr/bin/env bash | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this script specific for this repo of do we have it copied to multiple repos?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @dmage so far the thinking is that it would be copied to multiple repos, given that we don't have a good way of sharing scripts across multiple components. It could be placed in library-go, but not all components use library-go. Also not all components use the same directories for their manifests. I'm definitely open to ideas on how to better handle this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@csrwng what about https://github.com/openshift/build-machinery-go ? cluster-image-registry-operator uses only one target from build-machinery, so it shouldn't be a problem to add a single target to other repositories.
See
cluster-image-registry-operator/Makefile
Lines 9 to 13 in e5877a8
| include $(addprefix ./vendor/github.com/openshift/build-machinery-go/make/, \ | |
| targets/openshift/bindata.mk \ | |
| ) | |
| $(call add-bindata,assets,./bindata/...,./bindata/,assets,pkg/assets/bindata.go) |
You can add something similar:
$(call add-profile-manifests,./manifests/,./profile-patches/)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That sounds promising, will try it out. Thx!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Submitted openshift/build-machinery-go#26 - will update this PR when that merges
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
/remove-lifecycle stale |
313dc3f to
fbefa25
Compare
fbefa25 to
2f588b0
Compare
|
@dmage I've now updated this PR to bump to the latest build-machinery-go and I'm now using that add a patch for ibm-cloud-managed. |
2f588b0 to
30c347e
Compare
|
/retest |
|
/assign @ricardomaraschini |
| GOLANGCI_LINT_CACHE = $(PWD)/_output/golangci-lint-cache | ||
| GOLANGCI_LINT_VERSION = v1.24 | ||
|
|
||
| GO_REQUIRED_MIN_VERSION = 1.14 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any special reason for not going with a newer version? I have noticed here that if it is not set we go for 1.15.2.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason I added this here, is that verify previously failed (looks like your CI test is using an older go version):
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/643/pull-ci-openshift-cluster-image-registry-operator-master-verify/1376950809396252672
Note that this is the minimum version. It's fine to use a newer release.
| @@ -0,0 +1,86 @@ | |||
| apiVersion: apps/v1 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you mind giving me some explanation on how this is going to work? I mean, with this extra manifest here isn't CVO going to create two distinct deployments (07-operator.yaml and 07-operator-ibm-cloud-managed.yaml)? Is there some special handling happening @ cvo side to handle this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically for any given installation of openshift only one cluster profile is active. The CVO will only apply manifests that contain an annotation for the active cluster profile.
Ref: openshift/cluster-version-operator#404
Enhancement: openshift/enhancements#200
| @@ -0,0 +1,3 @@ | |||
| // required for gomod to pull in packages. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you split this PR into two separated commits? One with vendoring stuff and the other with the changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ricardomaraschini it is in 2 separate commits
|
/retest |
ricardomaraschini
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: csrwng, ricardomaraschini The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold |
|
/retest |
|
/hold cancel |
|
/retest |
|
@csrwng: This pull request references Bugzilla bug 1948714, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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: GitHub didn't allow me to request PR reviews from the following users: csrwng. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
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. |
|
/bugzilla refresh |
|
@csrwng: This pull request references Bugzilla bug 1948714, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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: GitHub didn't allow me to request PR reviews from the following users: csrwng. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
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. |
|
/retest |
|
@csrwng: All pull requests linked via external trackers have merged: Bugzilla bug 1948714 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
Part 2 of cluster profiles support for IBM Cloud.
Introduces a directory that will contain profile-specific patches.
Profile-specific manifests are generated with 'make profile-manifests'
and 'hack/verify-profile-manifests.sh' (called by 'make verify') verifies
that the manifests directory is up to date.
On IBM Cloud the Image Registry operator needs to run on worker nodes, thus the
master node selector needs to be removed from the operator deployment
manifest.