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

Allows running ManageIQ orchestrator on pure Kubernetes #17845

Closed
sebastien-prudhomme opened this issue Aug 10, 2018 · 1 comment · Fixed by #19500
Closed

Allows running ManageIQ orchestrator on pure Kubernetes #17845

sebastien-prudhomme opened this issue Aug 10, 2018 · 1 comment · Fixed by #19500
Assignees
Labels

Comments

@sebastien-prudhomme
Copy link

Hi,

Currently ManageIQ orchestrator can not run on pure Kubernetes because it uses OpenShift API to create an OpenShift DeploymentConfig object.

Enable a mode that permits to use a native Kubernetes Deployment object instead of the OpenShift one.

@miq-bot miq-bot added the stale label Feb 12, 2019
@miq-bot
Copy link
Member

miq-bot commented Feb 12, 2019

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

@carbonin carbonin added pinned and removed stale labels Nov 6, 2019
carbonin added a commit to carbonin/manageiq that referenced this issue Nov 12, 2019
This will allow the orchestrator to run on either OpenShift
or Kubernetes by using only objects supported by both

Fixes ManageIQ#17845
carbonin added a commit to carbonin/manageiq that referenced this issue Nov 12, 2019
This will allow the orchestrator to run on either OpenShift
or Kubernetes by using only objects supported by both

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

Successfully merging a pull request may close this issue.

3 participants