Skip to content
This repository was archived by the owner on May 24, 2020. It is now read-only.

[WIP] Helm chart to deploy GCS #14

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

[WIP] Helm chart to deploy GCS #14

JohnStrunk wants to merge 2 commits into from

Conversation

@JohnStrunk
Copy link
Member

@JohnStrunk JohnStrunk commented Oct 1, 2018

I'm working on a Helm chart to deploy GCS. This PR is just to make the progress public for those interested.

Fixes #12

Current status:

  • The components come up (etcd operator, etcd, gd2, gluster-csi)
  • Devices are not added to gd2 yet, so no storage is available.

@ghost ghost assigned JohnStrunk Oct 1, 2018
@ghost ghost added the in progress label Oct 1, 2018
@kshlm
Copy link
Member

kshlm commented Oct 11, 2018

I tried to test this out. Centos-atomic does not have socat available which is required for Helm to work, and centos-atomic doesn't provide an easy way to get it installed using Ansible either.
So I'm planning to switch the base to regular centos which doesn't have the issue.

@JohnStrunk
Copy link
Member Author

JohnStrunk commented Oct 11, 2018

I tried to test this out. Centos-atomic does not have socat available which is required for Helm to work, and centos-atomic doesn't provide an easy way to get it installed using Ansible either.
So I'm planning to switch the base to regular centos which doesn't have the issue.

Looks like there's a related issue open against kubespray: kubernetes-sigs/kubespray#2879

@amarts amarts mentioned this pull request Oct 14, 2018
Closed
@JohnStrunk JohnStrunk mentioned this pull request Nov 13, 2018
Merged
@JohnStrunk
Initial helm chart that can deploy etcd
68f4aec 
- Deploys etcd-operator
- Creates an etcd cluster

Signed-off-by: John Strunk <[email protected]>
@JohnStrunk
Add helm deploy instructions
6b4a9a3 
Signed-off-by: John Strunk <[email protected]>
@JohnStrunk
Copy link
Member Author

JohnStrunk commented Nov 20, 2018

With #69 merged, Helm should now work, so this approach is now viable. However, this PR is significantly out of date wrt how we are currently deploying GCS components.

@JohnStrunk JohnStrunk added the do-not-merge indicates that PR should not be merged label Jan 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

@JohnStrunk JohnStrunk

Labels

do-not-merge indicates that PR should not be merged in progress

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@JohnStrunk @kshlm