Skip to content

Problem of AWS dependency to use operator SDK #5562

@ar-bella-jeong

Description

@ar-bella-jeong

Type of question

Open question

Question

What did you do?

Our system is consisted of AWS resources such as EKS, ECR and so on.
I plan to use Operator SDK to develop k8s operators because it is already working like kubebuilder especially in case of go based operator.
However, unfortunately ECR provides only IAM authentication to make the authorization token, Operator sdk provides only CA authentication method to use private image registry. That's why I can't use whole solutions in aws environment.

What did you expect to see?

I wonder someone uses AWS resources with operator sdk who also uses OLM.
I worry about that we have to use kubebuilder instead of operator sdk due to AWS vendor dependency.
Is there anyone use aws resources with operator sdk? If you know and don't mind, please give me any advice.

Environment

Operator type:

/language go

Kubernetes cluster type:
AWS EKS v1.20

$ operator-sdk version

$ go version (if language is Go)

$ kubectl version

Additional context

Metadata

Metadata

Labels

language/goIssue is related to a Go operator projectlifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.triage/needs-informationIndicates an issue needs more information in order to work on it.triage/supportIndicates an issue that is a support question.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions