Basic, basic, foundational question


#1

We’re trying to get Spinnaker to work with a simple Deploy (Manifest) pipeline on EKS. When we talk about a new deploy and point it at a server, is it trying to create a new EKS cluster, and how would we be able to tell, since we’re not getting errors in either AWS or (that I can see) clouddriver?

I’ve been looking through the spinnaker documentation and am having a hard time finding out where you deploy to a new cluster that you create in Spinnaker (which our install doesn’t seem to want to do, despite having an AWS account with sufficient permissions), or to an already-existing cluster (which it doesn’t seem to want to do, because we keep getting “waiting for manifest to stabilize” until the deploy task dies (I created another thread for this particular problem).

Specifically about accounts: I know it can’t create a new cluster with our kubernetes account defined in .kube/config and exposed to Spinnaker via .hal/config, and the names of the aws account/kubernetes account shouldn’t have an impact on each other, but I’m having trouble nailing down not only where the problem is, but what behavior I should be expecting.

Is there any documentation you could point us to that goes into this specific set of concepts in detail?

Thank you in advance.


#2

I think I have a partial answer here. I tried changing the AWS account name to match the Kubernetes account name, and Halyard didn’t like it so much.

(venv) admin@spin01:~/.hal$ sudo hal deploy apply
+ Get current deployment
  Success
- Prep deployment
  Failure
Problems in default.provider.aws.ngs-aws-main:
- WARNING No validation for the AWS provider has been
  implemented.

Problems in default.provider.aws.eks-test-dev-token-user:
- WARNING No validation for the AWS provider has been
  implemented.

Problems in default.provider:
! ERROR Account "eks-test-dev-token-user" appears more than
  once
? Change the name of the account in kubernetes

- Failed to prep Spinnaker deployment
(venv) admin@spin01:~/.hal$

#3

Howdy @rhuffman. I’m having a bit of trouble understanding your question. Are you asking if adding a new Kubernetes account will create a new EKS cluster? Or are you asking if you can name your AWS account the same name as a Kubernetes account?

I wrote up a blog post about Spinnaker accounts and how they relate to Kubernetes that I think may be helpful. If it isn’t, let me know and I’ll help in any way I can. You can find the blog post here.