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

Remove node status from crd resources #1710

Open
davzucky opened this issue Aug 5, 2020 · 2 comments
Open

Remove node status from crd resources #1710

davzucky opened this issue Aug 5, 2020 · 2 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@davzucky
Copy link

davzucky commented Aug 5, 2020

Bug Report

The current release file of crds.yaml add for each resources a node status. This node is valid, however it should not be here for the original deployment.

What did you do?
I tried to deployed olm using pulumi kubernetes. This is failing because the crd resources have a node status

What did you expect to see?
Expect to be able to deploy olm using pulumi below

import pulumi
from pulumi_kubernetes.yaml import  ConfigFile

release = "0.15.1"
base_url = f"https://github.com/operator-framework/operator-lifecycle-manager/releases/download/{release}"
crds_url = f"{base_url}/crds.yaml"
olm_url = f"{base_url}/olm.yaml"
crds = ConfigFile("crds", crds_url)
olm = ConfigFile("olm", olm_url, opts=pulumi.ResourceOptions(depends_on=[crds]))

Possible Solution
Remove the node status from the crd resources

@exdx exdx added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. labels Aug 27, 2020
@stale
Copy link

stale bot commented Oct 26, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Oct 26, 2020
@openshift-ci-robot openshift-ci-robot added triage/unresolved Indicates an issue that can not or will not be resolved. and removed wontfix labels Oct 27, 2020
@stale
Copy link

stale bot commented Dec 26, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Development

No branches or pull requests

3 participants