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

Add manifests for deploying core etcd and etcd proxy #1

Merged
merged 2 commits into from May 30, 2018
Merged

Conversation

xmudrii
Copy link
Owner

@xmudrii xmudrii commented May 28, 2018

No description provided.

@xmudrii xmudrii changed the title experimental: add manifests for deploying etcd and etcdproxy Add manifests for deploying etcd and etcdproxy May 28, 2018
apiVersion: v1
kind: Pod
metadata:
name: etcd-pod
Copy link
Collaborator

Choose a reason for hiding this comment

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

rename this. It's the core-etcd, right?

Copy link
Owner Author

Choose a reason for hiding this comment

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

Done

args: ["--listen-client-urls=http://0.0.0.0:2379", "--advertise-client-urls=http://0.0.0.0:2379"]
ports:
- name: etcd
containerPort: 2379
Copy link
Collaborator

Choose a reason for hiding this comment

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

please make a service that exposes this.

Copy link
Owner Author

Choose a reason for hiding this comment

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

The service is added in #2

- name: etcdproxy
image: quay.io/coreos/etcd:v3.2.18
command: ["/usr/local/bin/etcd", "grpc-proxy", "start"]
args: ["--endpoints=http://172.17.0.3:2379", "--namespace=/exp", "--listen-addr=0.0.0.0:23790"]
Copy link
Collaborator

Choose a reason for hiding this comment

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

ip address is not known ahead of time, so this won't work generically.

Copy link
Collaborator

Choose a reason for hiding this comment

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

reference the service, not the pod.

Copy link
Owner Author

@xmudrii xmudrii May 29, 2018

Choose a reason for hiding this comment

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

@xmudrii xmudrii changed the title Add manifests for deploying etcd and etcdproxy Add manifests for deploying core etcd and etcd proxy May 29, 2018
- name: etcdproxy
image: quay.io/coreos/etcd:v3.2.18
command: ["/usr/local/bin/etcd", "grpc-proxy", "start"]
args: ["--endpoints=http://etcd-svc-1.etcd.svc.cluster.local:2379", "--namespace=/exp", "--listen-addr=0.0.0.0:2379"]
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: .cluster.local is configurable, so you probably want to end at .svc

Copy link
Owner Author

Choose a reason for hiding this comment

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

Changed

image: quay.io/coreos/etcd:v3.2.18
env:
- name: ETCD_CERT_FILE
value: "/etc/server-certs/server.pem"
Copy link
Collaborator

Choose a reason for hiding this comment

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

this wasn't here before, right? Adding this means you have to add trust certs to have the proxy trust the core etcd, right?

Copy link
Owner Author

Choose a reason for hiding this comment

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

No, it wasn't. It was in #2 and I added it here when updating.

Not sure I'm following, but in this case I have to add server certs here, and client certs to etcd proxy. Client certs were not added before, but I updated the PR to include those as well.

Nothing else is needed, I think.

@deads2k
Copy link
Collaborator

deads2k commented May 29, 2018

Looks good enough to me if you want to start here. I'm not certain it runs though.

@xmudrii
Copy link
Owner Author

xmudrii commented May 29, 2018

@deads2k Updated the PR to include client certs for etcd proxy. I have tested the manifests on my two clusters (one ran using local-up-cluster.sh, another running on DO), and the manifests work on both, so I guess they're okay.

args: ["--endpoints=https://etcd-svc-1.etcd.svc:2379", "--namespace=/example", "--listen-addr=0.0.0.0:2379", "--cacert=/etc/certs/ca.pem", "--cert=/etc/certs/client.pem", "--key=/etc/certs/client-key.pem"]
volumeMounts:
- name: client-certs
mountPath: "/etc/certs"
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit, you'll want these to be specific in teh final version

Copy link
Collaborator

@deads2k deads2k left a comment

Choose a reason for hiding this comment

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

good place to start

@deads2k deads2k merged commit 871c535 into master May 30, 2018
@xmudrii xmudrii deleted the experimental branch May 30, 2018 14:00
@xmudrii xmudrii added this to the Evaluation 1 milestone Jun 8, 2018
xmudrii added a commit that referenced this pull request Jun 21, 2018
@xmudrii xmudrii added the ready-for-review Indicates that a Pull Request is ready for review. label Aug 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-review Indicates that a Pull Request is ready for review.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants