v1.0.1
Bug Fixes
- Fixed a bug with
run packagemanifeststhat caused the underlying registry pod to fail to start. Changed the registry pod image fromquay.io/openshift/origin-operator-registry:latesttoquay.io/operator-framework/upstream-registry-builder:latest. (#3895) - Resolved an issue that caused bundle validation to unnecessarily restrict CSV names to a specific format. Now, only DNS-1123 subdomain validity is verified. (#3888)
- Fix an issue in
run packagemanifestswhere the registry server writes files in locations that require root. (#3895) - Fixed debug logging in the
bundle validatesubcommand ofoperator-sdk. (#3899) generate <bundle|packagemanifests>now generates a CSV base with only theAllNamespacesinstall mode supported by default, since projects are cluster-scoped by default. (#3899)- When generating bundles and packagemanifests, remove
metadata.namespacefrom namespaced resources when writing them into themanifestsdirectory to avoid validation errors. (#3899) - Fixed a bug that caused the Helm operator not to set the
InstallSuccessfulandUpgradeSuccessfulstatus reasons when the status update fails during installation and upgrade. (#3899) - In Helm projects, fix operator permissions for Openshift deployments by adding a
<resource>/finalizersrule in the operator's role. (#3899) - Prevent
run packagemanifestsfrom creating an OperatorGroup if one already exists in a namespace, and use that OperatorGroup if its target namespaces exactly match those passed in--install-mode. See #3681. (#3899) - Stop reconciling tasks when the event raised is a rescue in Ansible-based Operators. More info: Bugzilla 1856714. (#3650)
- When scaffolding scorecard configurations, use release versions instead of
latestin image tags. (#3899) generate <bundle|packagemanifests>will populate a CSV'swebhookDefinition[].deploymentNameby selecting an input Deployment via its PodTemplate labels using a webhook Service's label selectors, defaulting to "<service.metadata.name>-service" if none is selected. (#3904)