Closed mart3051 closed 5 years ago
My bad it was due to resource crunch. My cluster had only one node and auto scaling disabled . Enabled the auto scaling and made max size=3 and the google auth pod which was not getting scheduled and had caused the issue got scheduled and the issue got resolved
Steps to recreate:- 1.
kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account)
Gotclusterrolebinding.rbac.authorization.k8s.io/cluster-admin-binding created
2.sc check
Got the expected result Dependency check passed. You are good to go. 3.sc install
O/pService Catalog installed successfully
kubectl get deployment -n service-catalog
O/pNAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE apiserver 1 1 1 1 2m controller-manager 1 1 1 1 2m etcd-cluster-backup-sidecar 1 1 1 1 2m etcd-operator 1 1 1 1 3m
5.sc add-gcp-broker
O/pusing project: kubeservicebroker27 enabling a GCP API: servicebroker.googleapis.com enabling a GCP API: bigquery-json.googleapis.com enabling a GCP API: bigtableadmin.googleapis.com enabling a GCP API: ml.googleapis.com enabling a GCP API: pubsub.googleapis.com enabling a GCP API: spanner.googleapis.com enabling a GCP API: sqladmin.googleapis.com enabling a GCP API: storage-api.googleapis.com enabled required APIs: servicebroker.googleapis.com bigquery-json.googleapis.com bigtableadmin.googleapis.com ml.googleapis.com pubsub.googleapis.com spanner.googleapis.com sqladmin.googleapis.com storage-api.googleapis.com generated the key at: /tmp/service-catalog-gcp290646345/key.json Broker "default", already exists The Service Broker has been added successfully.
6.kubectl describe clusterservicebrokers/gcp-broker
O/p `Name: gcp-broker Namespace:Labels:
Warning ErrorGettingAuthCredentials 18s (x13 over 40s) service-catalog-controller-manager Error getting broker auth credentials: secrets "gcp-svc-account-secret" not found`
Step 5 o/p is not inline to Step 6. Memory is also good. Expectation:-Step 5 should give success only if service broker is created successfully. Moreover the reason for absence of gcp-svc-account-secret is not apparent.
Additional details
kubectl top nodes
O/pNAME CPU(cores) CPU% MEMORY(bytes) MEMORY% gke-mcsbcluster-default-pool-7cc9386e-zqh1 139m 14% 883Mi 33%
sc version
O/psc version 0.1.1 linux/amd64