Closed jotak closed 1 week ago
@jotak: This pull request references NETOBSERV-1731 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.17.0" version, but no target version was set.
New images:
They will expire after two weeks.
To deploy this build:
# Direct deployment, from operator repo
IMAGE=quay.io/netobserv/network-observability-operator:fcf1333 make deploy
# Or using operator-sdk
operator-sdk run bundle quay.io/netobserv/network-observability-operator-bundle:v0.0.0-fcf1333
Or as a Catalog Source:
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: netobserv-dev
namespace: openshift-marketplace
spec:
sourceType: grpc
image: quay.io/netobserv/network-observability-operator-catalog:v0.0.0-fcf1333
displayName: NetObserv development catalog
publisher: Me
updateStrategy:
registryPoll:
interval: 1m
/LGTM
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 66.13%. Comparing base (
66c7a62
) to head (230c78a
). Report is 5 commits behind head on main.
@jotak: This pull request references NETOBSERV-1731 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.17.0" version, but no target version was set.
/label qe-approved
@jotak: This pull request references NETOBSERV-1731 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.17.0" version, but no target version was set.
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jotak
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Description
Same with subnet labels / openshift auto-detect (NETOBSERV-1734)
This is to avoid confusion, since nillable bools are not managed properly in OLM forms They can be access from YAML
A longer-term solution will be to replace all our nillable bools with enums in a next API version
Dependencies
n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.