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.

Sign up for GitHub

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

Jump to bottom

Added k8s manifests #158

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Added k8s manifests #158

wants to merge 3 commits into from

Conversation

ckt114
Copy link

@ckt114 ckt114 commented Mar 1, 2019 •
edited
Loading

Manifests to run Cronicle in Kubernetes.

@ckt114 ckt114 mentioned this pull request Mar 1, 2019
Closed
@toshyak
Copy link

toshyak commented Jul 31, 2019

@trankchung thanks for your contribution, I found it very useful. Can you please clarify the purpose of cronicle client deployment? I didn't find anything about it in cronicle documentation. Thanks in advance!

@ckt114
Copy link
Author

ckt114 commented Jul 31, 2019

@toshyak Cronicle designed using client/server model. In short, the master manages the jobs and the clients/slaves run the jobs. If no client then the master must be told it can run jobs. Having many clients allow distribution of loads.

@toshyak
Copy link

toshyak commented Aug 1, 2019

@trankchung thanks for the response, now I got it!

@Palezvar
Copy link

@trankchung , I have a question for you. When I deploy these yaml files on my microk8s, I noticed that the services show cluster IP but no external IP. Shouldn't the type for service be Loadbalancer for external access?

I am asking because I am not able to reach portal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@ckt114 @toshyak @Palezvar