Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚀 Dockerize operator to private container repository hub #26

Open
sydrawat01 opened this issue Nov 26, 2023 · 1 comment
Open

🚀 Dockerize operator to private container repository hub #26

sydrawat01 opened this issue Nov 26, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request feature-req A good "to-have" feature, following best practices.

Comments

@sydrawat01
Copy link
Member

Currently, we are storing the operator docker image in a public dockerhub repository.

  • Use quay.io to store the k8s-operator docker image.
  • We need pull secrets so that the kubebuilder manager can pull this private image when using make deploy.

Build and push works after we login using quay secrets:

make docker-build docker-push IMG=quay.io/pwncorp/k8s_operator NS=webapp

But when using make deploy, the pod create by kubebuilder fails to pull the secret container image from quay:

make deploy IMG=quay.io/pwncorp/k8s_operator NS=webapp
@sydrawat01 sydrawat01 added the enhancement New feature or request label Nov 26, 2023
@sydrawat01 sydrawat01 self-assigned this Nov 26, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in ☁️ kanban Nov 26, 2023
@sydrawat01 sydrawat01 moved this from 🆕 New to 📋 Backlog in ☁️ kanban Nov 26, 2023
@sydrawat01
Copy link
Member Author

As a workaround for now, we have made the k8s_operator docker image public so that we can deploy the operator on the private GKE cluster.

@sydrawat01 sydrawat01 added the feature-req A good "to-have" feature, following best practices. label Dec 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature-req A good "to-have" feature, following best practices.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant