Using client-go to `kubectl apply` against the Kubernetes API directly with multiple types in a single YAML file

• client-go

  38 8,595 9.3 Go

  Go client for Kubernetes.

  

I'm using https://github.com/kubernetes/client-go and all works well.

• api

  8 621 9.2 Go

  The canonical location of the Kubernetes API definition. (by kubernetes)

  

I understand that I need to do some (un)marshalling of the YAML bytes into the correct API types defined in package: https://github.com/kubernetes/api

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• apimachinery

  5 781 8.9 Go
  

I found this issue to be helpful: https://github.com/kubernetes/client-go/issues/193The decoder lives here: https://github.com/kubernetes/apimachinery/tree/master/pkg/runtime/serializer

• eksctl

  59 4,781 9.5 Go

  The official CLI for Amazon EKS

  

Edit: Because I need to do this for more than one cluster and am creating clusters programmatically (AWS EKS API + CloudFormation/eksctl), I would like to minimize the overhead of creating ServiceAccounts across many cluster contexts, across many AWS accounts. Ideally, the only authentication step involved in creating my clientset is using aws-iam-authenticator to get a token using cluster data (name, region, CA cert, etc). There hasn't been a release of aws-iam-authenticator for a while, but the contents of master allow for the use of a third-party role cross-account role and external ID to be passed. IMO, this is cleaner than using a ServiceAccount (and IRSA) because there are other AWS services the application (the backend API which creates and applies add-ons to these clusters) needs to interact with.

• aws-iam-authenticator

  9 2,137 7.6 Go

  A tool to use AWS IAM credentials to authenticate to a Kubernetes cluster

  

Edit: Because I need to do this for more than one cluster and am creating clusters programmatically (AWS EKS API + CloudFormation/eksctl), I would like to minimize the overhead of creating ServiceAccounts across many cluster contexts, across many AWS accounts. Ideally, the only authentication step involved in creating my clientset is using aws-iam-authenticator to get a token using cluster data (name, region, CA cert, etc). There hasn't been a release of aws-iam-authenticator for a while, but the contents of master allow for the use of a third-party role cross-account role and external ID to be passed. IMO, this is cleaner than using a ServiceAccount (and IRSA) because there are other AWS services the application (the backend API which creates and applies add-ons to these clusters) needs to interact with.

• k8s

  1 596 10.0 Go

  Discontinued A simple Kubernetes Go client (by ericchiang)

Edit: I have recently found https://github.com/ericchiang/k8s. It's definitely simpler to use than client-go, at a high-level, but doesn't support this behavior.

Suggest a related project