Spinnaker deployment on AWS EKS

1/23/2020

I have a current deployment of spinnaker in one of my AWS EKS cluster. Initially, the pods were failing due to the readiness pointing to the localhost. So I updated the readiness probe of deployments for almost all the micro-services (spin-orca, spin-clouddriver, etc.,) Initial readinessprobe for clouddriver was

readinessProbe:
          exec:
            command:
            - wget
            - --no-check-certificate
            - --spider
            - -q
            - http://localhost:7002/health
          failureThreshold: 3
          periodSeconds: 10
          successThreshold: 1

I updated it from localhost to the tcpSocket as given below:

readinessProbe:
          failureThreshold: 3
          initialDelaySeconds: 5
          periodSeconds: 10
          successThreshold: 1
          tcpSocket:
             port: 7002

Clouddriver started after this update, but I enabled jenkins & trying to do a hal deploy apply It fails with

The Deployment "spin-clouddriver" is invalid:
  spec.template.spec.containers[0].readinessProbe.tcpSocket: Forbidden: may not
  specify more than 1 handler type

Can anyone guide me on this issue?

-- Sandy
amazon-eks
amazon-web-services
jenkins
kubernetes
spinnaker-halyard

0 Answers