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

[BUG] CRC docs missing information about how to use container registry #1418

Closed
rexroof opened this issue Jul 24, 2020 · 4 comments
Closed
Assignees
Labels
kind/documentation Documentation issues. priority/major status/pinned Prevents the stale bot from closing the issue

Comments

@rexroof
Copy link

rexroof commented Jul 24, 2020

Sorry if this is the wrong place for this:

minishift had pretty good documentation about how to use the internal container registry, I can't find that documentation for CRC.

here are some questions I've been trying to figure out:

should I use
image-registry.openshift-image-registry.svc:5000 for my registry address or should I use default-route-openshift-image-registry.apps-crc.testing ?
I notice that I have varying success with getting the SSL certificates on these hostnames to be recognized.
I understand the issues around self-signed certificates but I am trying to work out the "best practices" as suggested by this project. do I need to manually change the internal settings of my CRC cluster to allow insecure registries?
Do I need to use one of these for docker push/pull and another for my image urls in my container manifests?
Do I need to create an imagePullSecret to use this registry? How is that best accomplished?

I'm wondering if the lack of documentation around the internal container registry means that I shouldn't be pushing my custom containers to this registry and I should be using some other method to deploy my application on openshift 4 / CRC.

@rexroof rexroof added the kind/bug Something isn't working label Jul 24, 2020
@praveenkumar praveenkumar added the kind/documentation Documentation issues. label Jul 28, 2020
@praveenkumar
Copy link
Member

@rexroof Thanks for pointing it out, we will try to put note https://docs.okd.io/3.11/minishift/openshift/openshift-docker-registry.html like this one.

@kowen-rh kowen-rh self-assigned this Jul 28, 2020
@kowen-rh
Copy link
Contributor

@praveenkumar I'll need more information about how to document this as outlined in the original issue (great questions, by the way).

It seems to me that we could use a dedicated procedure for this task.

@kowen-rh kowen-rh added priority/major and removed kind/bug Something isn't working labels Jul 28, 2020
@kowen-rh kowen-rh added this to To do in Documentation Jul 28, 2020
@stale
Copy link

stale bot commented Sep 26, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale Issue went stale; did not receive attention or no reply from the OP label Sep 26, 2020
@anjannath anjannath added status/pinned Prevents the stale bot from closing the issue and removed status/stale Issue went stale; did not receive attention or no reply from the OP labels Oct 8, 2020
kowen-rh added a commit to kowen-rh/crc that referenced this issue Dec 2, 2020
kowen-rh added a commit to kowen-rh/crc that referenced this issue Dec 4, 2020
kowen-rh added a commit to kowen-rh/crc that referenced this issue Dec 4, 2020
@kowen-rh
Copy link
Contributor

Fixed by #1418.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Documentation issues. priority/major status/pinned Prevents the stale bot from closing the issue
Projects
No open projects
Documentation
  
Done
Development

No branches or pull requests

4 participants