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

Allow push to internal registry #721

Closed
matejvasek opened this issue Dec 14, 2021 · 3 comments
Closed

Allow push to internal registry #721

matejvasek opened this issue Dec 14, 2021 · 3 comments
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@matejvasek
Copy link
Contributor

matejvasek commented Dec 14, 2021

Make it possible to push to cluster internal registries.

  • User should be able to push to internal registry with cluster local URL
    (e.g. image-registry.openshift-image-registry.svc:5000).

  • If needed the cluster internal CA should be trusted for the connection.

  • If the cluster is OpenShift we should use it's internal registry by default, i.e. not prompt user for registry.

@matejvasek
Copy link
Contributor Author

related PRs: #718, #704, #688.

@matejvasek matejvasek self-assigned this Dec 14, 2021
@github-actions
Copy link
Contributor

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 15, 2022
@zroubalik
Copy link
Contributor

@matejvasek this is done, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants