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

Phony manifests #730

Closed
wants to merge 40 commits into from
Closed

Phony manifests #730

wants to merge 40 commits into from

Conversation

cybertron
Copy link
Collaborator

Is this a BUG FIX or a FEATURE ?:

Uncomment only one, leave it on its own line:

/kind bug

/kind enhancement

What this PR does / why we need it: The manifests target in the Makefile is currently broken because we added a manifests directory. This fixes "make manifests" so it works correctly.

Special notes for your reviewer:

Release note:

NONE

openshift-merge-robot and others added 30 commits November 11, 2020 22:32
The internal Networking team needs to be able to approve and review.

Signed-off-by: Brad P. Crochet <[email protected]>
[CARRY] Add midstream reviewers and approvers
[CARRY] Make operator bundle for OLM
```
Image build failed. Error in plugin pin_operator_digest: while
constructing a mapping\n  in
"/tmp/tmpii4h0l34/openshift-kubernetes-nmstate-operator-bundle/manifests/kubernetes-nmstate-operator.v4.7.0.clusterserviceversion.yaml",
line 5, column 5\nfound duplicate key "certified" with value "false"
(original value: "false")\n  in
"/tmp/tmpii4h0l34/openshift-kubernetes-nmstate-operator-bundle/manifests/kubernetes-nmstate-operator.v4.7.0.clusterserviceversion.yaml",
line 26, column 5\n\nTo suppress this check see:\n
http://yaml.readthedocs.io/en/latest/api.html#duplicate-keys\n\nDuplicate
keys will become and error in future releases, and are errors\nby
default when using the new API.\n. OSBS build id:
openshift-kubernetes-nmstate-op-rhaos-47-rhel-8-2faf9-1
```
Remove duplicated 'certified' key in CSV
Inadverdently used 'RELATED_IMAGES_' instead of 'RELATED_IMAGE_'
[CARRY] Correct the env var used for the handler image
[CARRY] Add securitycontextconstraints to CSV
This is causing a conflict with ART tooling.
[CARRY] Remove RELATED_IMAGE_ from the handler image env var
This adds the privileged SCC for the nmstate-handler serviceaccount.
The nmstate-operator serviceaccount was not enough.
Multiple sa's can be specificed in the CSV.

Signed-off-by: Brad P. Crochet <[email protected]>
[CARRY] Add cluster rules for nmstate-handler sa
Originally I placed the nmstate-handler SA under the cluster
permission. It needed to be in the namespaced section.

Signed-off-by: Brad P. Crochet <[email protected]>
[CARRY] Move the nmstate-handler sa to the correct section
The example as given doesn't really work. It's better to have a working
sample.

Signed-off-by: Brad P. Crochet <[email protected]>
Change example name to nmstate, and add nodeSelector
…nshift-4.7-openshift-kubernetes-nmstate-operator

Updating openshift-kubernetes-nmstate-operator builder & base images to be consistent with ART
…nshift-4.7-openshift-kubernetes-nmstate-handler

Updating openshift-kubernetes-nmstate-handler builder & base images to be consistent with ART
The example in the CSV manifest is incorrect. The nodeSelected needs to be
represented as an object, not as a string.

Signed-off-by: Brad P. Crochet <[email protected]>
Bug 1918958: Fix the example NMState instance in the manifest
…nshift-4.7-openshift-kubernetes-nmstate-operator

Updating openshift-kubernetes-nmstate-operator builder & base images to be consistent with ART
openshift-merge-robot and others added 10 commits February 2, 2021 08:20
…nshift-4.7-openshift-kubernetes-nmstate-handler

Updating openshift-kubernetes-nmstate-handler builder & base images to be consistent with ART
The internal Networking team needs to be able to approve and review.

Signed-off-by: Brad P. Crochet <[email protected]>
Without this, make sees the manifests directory we added and thinks
the target is always up to date.
@kubevirt-bot kubevirt-bot added the release-note-none Denotes a PR that doesn't merit a release note. label Apr 21, 2021
@kubevirt-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign phoracek
You can assign the PR to them by writing /assign @phoracek in a comment when ready.

The full list of commands accepted by this bot can be found 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

@kubevirt-bot kubevirt-bot requested review from RamLavi and yboaron April 21, 2021 23:26
@kubevirt-bot kubevirt-bot added the dco-signoff: no Indicates the PR's author has not DCO signed all their commits. label Apr 21, 2021
@kubevirt-bot
Copy link
Collaborator

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

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.

@kubevirt-bot
Copy link
Collaborator

Hi @cybertron. Thanks for your PR.

I'm waiting for a nmstate member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@kubevirt-bot kubevirt-bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XL labels Apr 21, 2021
@cybertron
Copy link
Collaborator Author

Argh, opened this against the wrong repo.

@kubevirt-bot
Copy link
Collaborator

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the nmstate org. You can then trigger verification by writing /verify-owners in a comment.

  • cybertron
    • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
    • OWNERS
  • celebdor
    • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
    • OWNERS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dco-signoff: no Indicates the PR's author has not DCO signed all their commits. do-not-merge/invalid-owners-file kind/bug needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/XL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants