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

Load docker images only on image_registry host #617

Merged
merged 3 commits into from
Oct 29, 2019

Conversation

to-bar
Copy link
Contributor

@to-bar to-bar commented Oct 17, 2019

No description provided.

@to-bar to-bar force-pushed the feature/k8s-upgrade-offline branch from 6a8d3f7 to 4bcc372 Compare October 23, 2019 17:35
@to-bar to-bar changed the title Fixes for K8s Load docker images only on image_registry host Oct 23, 2019
@to-bar to-bar force-pushed the feature/k8s-upgrade-offline branch 2 times, most recently from f1976d3 to 9f368b7 Compare October 23, 2019 17:49
@to-bar to-bar force-pushed the feature/k8s-upgrade-offline branch from 9f368b7 to c05141e Compare October 23, 2019 17:56
@to-bar to-bar marked this pull request as ready for review October 23, 2019 17:57
@to-bar to-bar merged commit bef52dc into hitachienergy:develop Oct 29, 2019
@to-bar to-bar deleted the feature/k8s-upgrade-offline branch October 29, 2019 08:58
to-bar added a commit to to-bar/epiphany that referenced this pull request Oct 29, 2019
* Load docker images only on image_registry host

* Use local image registry by default for auth-service and rabbitmq
to-bar added a commit that referenced this pull request Oct 29, 2019
* Load docker images only on image_registry host

* Use local image registry by default for auth-service and rabbitmq
to-bar added a commit to to-bar/epiphany that referenced this pull request May 6, 2020
* Load docker images only on image_registry host

* Use local image registry by default for auth-service and rabbitmq
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

Successfully merging this pull request may close these issues.

3 participants