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

Dynamically get host IP #9

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

Dynamically get host IP #9

wants to merge 10 commits into from

Conversation

CelsoSantos
Copy link

No description provided.

@@ -1,7 +1,7 @@
version: "2"
services:
db:
image: arungupta/couchbase
image: CelsoSantos/couchbase
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is CelsoSantos/couchbase different from arungupta/couchbase?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not. I don't recall including that on the PR version, but it should stay with arungupta/couchbase

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of the files seems to use that image. Can you update the PR to revert back to arungupta/couchbase?

@arun-gupta
Copy link
Owner

Do you also have the steps to create a Couchbase cluster on Kubernetes?

@bdangit
Copy link

bdangit commented Jul 29, 2016

in worker-service.yml, line https://github.com/arun-gupta/docker-images/pull/9/files#diff-3babe52f94acf7e05c41f4da77e2acf1L23 true value must be wrapped with quotes 'true'. Kube's validator keeps screaming that env elements must all be string.

$ kubectl create -f worker-service.yml
error validating "worker-service.yml": error validating data: expected type string, for field spec.template.spec.containers[0].env[2].value, got bool; if you choose to ignore these errors, turn validation off with --validate=false

On some what of a related point, there's something about these pod/service specs that doesn't seem right. Should the Master and Worker nodes be all within the same Couchbase K8s Service? When we expose the couchbase service, which one would we choose? If we choose the master thats a single point of failure. BTW, I make no claim at knowing how to setup a couchbase cluster. So maybe this is okay. 8)

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.

None yet

3 participants