Skip to content

REGISTRY_PUBLIC_PORT should not be mandatory #1319

@indor79

Description

@indor79

Feature and motivation

It is not uncommon with a registry that do not have a port in the path. When REGISTRY_PUBLIC_PORT is required we can not use does registries

Usage example

error: unable to push icr.io/cpopen/ibm-maximo-operator-catalog: failed to upload blob sha256:734a660836e9f0a771a4cb7853e2c61d33f52a09fb6697ec47e3cbce49157774: Post "https://quay.registry.foo.orgl:443/v2/cpopen/ibm-maximo-operator-catal
og/blobs/uploads/"

It should support https://quay.registry.foo.org/v2/cpopen/ibm-maximo-operator-catal
og/blobs/uploads/

Metadata

Metadata

Assignees

Labels

EnhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions