Hello,
Ok, so I have cloned the repo and modified the mongodb-service.yaml file,
so that
diff --git a/stable/mongodb-replicaset/templates/mongodb-service.yaml b/
stable/mongodb-replicaset/templates/mongodb-service.yaml
index d2903e7..bd952b9 100644
--- a/stable/mongodb-replicaset/templates/mongodb-service.yaml
+++ b/stable/mongodb-replicaset/templates/mongodb-service.yaml
@@ -14,8 +14,8 @@ metadata:
release: {{ .Release.Name }}
name: {{ template "fullname" . }}
spec:
- type: ClusterIP
- clusterIP: None
+ type: NodePort
+ clusterIP: 10.3.0.28
ports:
- name: peer
port: {{ .Values.port }}
then running, `helm install . --name test ` , i get:
➜ mongodb-replicaset git:(feature/mongo/update-type) ✗ kubectl get svc
(git)-[feature/mongo/update-type]
NAME CLUSTER-IP EXTERNAL-IP PORT(S)
AGE
test-mongodb-replicaset 10.3.0.28 <nodes> 27017:31876/TCP
3m
but now i am getting these errors:
Tolerations: <none>
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
9m 9m 2 default-scheduler Warning FailedScheduling [SchedulerPredicates
failed due to PersistentVolumeClaim is not bound:
"datadir-test-mongodb-replicaset-0", which is unexpected.,
SchedulerPredicates failed due to PersistentVolumeClaim is not bound:
"datadir-test-mongodb-replicaset-0", which is unexpected.,
SchedulerPredicates failed due to PersistentVolumeClaim is not bound:
"datadir-test-mongodb-replicaset-0", which is unexpected.,
SchedulerPredicates failed due to PersistentVolumeClaim is not bound:
"datadir-test-mongodb-replicaset-0", which is unexpected.,
SchedulerPredicates failed due to PersistentVolumeClaim is not bound:
"datadir-test-mongodb-replicaset-0", which is unexpected.,
SchedulerPredicates failed due to PersistentVolumeClaim is not bound:
"datadir-test-mongodb-replicaset-0", which is unexpected.]
9m 9m 1 default-scheduler Normal Scheduled Successfully assigned test-
mongodb-replicaset-0 to ip-10-0-10-229.eu-west-2.compute.internal
9m 9m 1 attachdetach Warning FailedMount Failed to attach volume
"pvc-88927d4f-5da9-11e7-93c0-06b40d25fce3" on node
"ip-10-0-10-229.eu-west-2.compute.internal" with: Error attaching EBS
volume "vol-03817831fe7d0c29e" to instance "i-04695822170b439ea":
IncorrectState: vol-03817831fe7d0c29e is not 'available'.
status code: 400, request id: b7de11b0-9650-4acc-b1f8-935dcfed4895
9m 9m 1 attachdetach Warning FailedMount Failed to attach volume
"pvc-88927d4f-5da9-11e7-93c0-06b40d25fce3" on node
"ip-10-0-10-229.eu-west-2.compute.internal" with: Error attaching EBS
volume "vol-03817831fe7d0c29e" to instance "i-04695822170b439ea":
IncorrectState: vol-03817831fe7d0c29e is not 'available'.
would i have to setup the volumes manually?
thanks
On Friday, June 30, 2017 at 1:00:04 PM UTC+1, Norman Khine wrote:
>
> Hello, I have installed mongodb using the helm chart,
> https://github.com/kubernetes/charts/blob/master/stable/mongodb-replicaset/templates/mongodb-service.yaml#L17,
>
> what is the correct way to update the Type and IP for this service,
> currently it is:
>
> ➜ k8s git:(master) kubectl describe svc trint-mongo-mongodb-replicaset
> --context
> zapotec
>
> (git)-[
> master]
> Name: test-mongo-mongodb-replicaset
> Namespace: dev
> Labels: app=mongodb-replicaset
> chart=mongodb-replicaset-0.2.0
> heritage=Tiller
> release=test-mongo
> Annotations: service.alpha.kubernetes.io/tolerate-unready-endpoints=true
> Selector: app=mongodb-replicaset,release=test-mongo
> Type: ClusterIP
> IP: None
> Port: peer 27017/TCP
> Endpoints: 10.2.6.6:27017,10.2.84.5:27017,10.2.84.6:27017
> Session Affinity: None
> Events: <none>
>
>
> or would I have to rebuild it from the helm chart?
>
> any advise is much appreciated
>
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
