WIP: Sync latest#126
Conversation
…e negatives Signed-off-by: Joe Lanford <joe.lanford@gmail.com> Upstream-repository: operator-registry Upstream-commit: 95c5e3bca1ac3abb3bf00f6b7345ddbd047e1524
Signed-off-by: Ben Luddy <bluddy@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: e731c70a5cd62ab1cab7658f1d17f810f525cd8e
Signed-off-by: Ankita Thomas <ankithom@redhat.com> Upstream-repository: operator-registry Upstream-commit: 9e88b877c8324d5fd027e512ad845b344cc4168a
Operator dependencies are expressed as properties, but there was initially a notion of dependencies as distinct from properties. For that reason, catalog-operator must support existing catalog images that serve separate Bundle.dependencies and Bundle.properties fields by translating the three legacy dependency types (olm.label, olm.package, and olm.gvk) into their corresponding properties. Signed-off-by: Ben Luddy <bluddy@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: c918a85eb7ef0c1ea58ebf27fabd8d2393afe9b3
TLS can still be enabled via flags, but it now applies to all three APIs since there is a single HTTP server per operator process. The -profiling flag is deprecated and does nothing. The profiling APIs are now always enabled, but they refuse to serve clients that do not present a verifiable certificate (see the new flag -client-ca). This effectively disables the profiling APIs when served over HTTP. Co-authored-by: Vu Dinh <vudinh@outlook.com> Co-authored-by: Alexander Greene <agreene@redhat.com> Signed-off-by: Ben Luddy <bluddy@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: f9381e0ce8e0addeb1abf55d44146a5e6e57074a
This line creates an info-level logger, writes a trace-level log to it, and discards the logger reference. This looks like cruft and is responsible for some heap churn. Signed-off-by: Ben Luddy <bluddy@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 8c8b18bacbc8033ef9d2a8847e730b3aa17247e6
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awgreene 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 |
8e05a67 to
2acdc65
Compare
|
|
/test e2e-aws-console-olm |
ca22f0d to
355d7d1
Compare
|
@awgreene: The following tests 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. |
This PR was created to test a hunch that #122 is failing due to a bad values.yaml file.