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

I want to use my privet registry for all images #3200

Open
yoyoraso opened this issue Apr 11, 2024 · 0 comments
Open

I want to use my privet registry for all images #3200

yoyoraso opened this issue Apr 11, 2024 · 0 comments

Comments

@yoyoraso
Copy link

Type of question

Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?

usage of olm in network isolated Environment

Question

What did you do?
I am trying olm in network isolated k8s cluster with privet registry and everything ok till point olm deploy the required operator which gets deployed with default image (which can't be pulled) and so on in next steps so I am asking how to determine images in one of the previous steps for olm so needed operator get deployed with new image not default one.

What did you expect to see?
better olm documentation on customising input.

What did you see instead? Under which circumstances?
just basic simple example which doesn't work in privet (network isolated) cluster.

Environment

  • operator-lifecycle-manager version:

v0.18.3
sha256:e74b2ac57963c7f3ba19122a8c31c9f2a0deb3c0c5cac9e5323ccffd0ca198ed

  • Kubernetes version information:

Client Version: v1.29.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.24.14+vmware.1

  • Kubernetes cluster kind:
    vanilla kubernetes

Additional context
Add any other context about the question here.

Thanks for whoever will answer :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant