Problem of AWS dependency to use operator SDK

[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

[jmrodri]

@ar-bella-jeong have you already done this with kubebuilder? Also, what specifically is failing on operator-sdk for you?

[acornett21]

@ar-bella-jeong I think you should look at AWS's ACK project here. They have controllers for alot of AWS services. They are available via helm and via OLM ie OpertorHub.io and OperatorHub inside of an OpenShift cluster.

[ar-bella-jeong]

@jmrodri I'm trying to use operator sdk yet. I found the solution ECR credential helper and then I'm testing the solution to use OLM. https://github.com/awslabs/amazon-ecr-credential-helper

[ar-bella-jeong]

@acornett21 Oh. I saw it at the first time. It might help me use all AWS resources with k8s. Thanks for the recommendation!

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.