search

operator-framework / operator-sdk

SDK for building Kubernetes applications. Provides high level APIs, useful abstractions, and project scaffolding.
https://sdk.operatorframework.io
Apache License 2.0
7.25k stars 1.75k forks source link

[meta] change ansible-/helm-operator binary and image names #4829

Open estroz opened 3 years ago

estroz commented 3 years ago

Feature Request

Describe the problem you need a feature to resolve.

The base "operators" (both binaries and images) for Ansible and Helm projects are currently called ansible-operator and helm-operator, respectively. This naming can be confusing because operator-sdk init --plugins=<ansible|helm> creates Ansible/Helm operator projects.

Describe the solution you'd like.

These base operators could be renamed to something more obvious. Some initial ideas, where "ansible" is used as the example language target:

Renaming will likely happen prior to v2.0 and be published alongside the current naming scheme, but a hard switch to a new name format would happen at v2.0 release time.

Would love input from Ansible and Helm folks!

/language ansible /language helm /kind feature

fabianvf commented 3 years ago

/cc @tima

fabianvf commented 3 years ago

Another alternative would be dropping the base image builds and instead using multi-stage dockerfiles where the user pulls in the relevant binaries (or builds from source but that seems more error prone)

estroz commented 3 years ago

@fabianvf can you give an example of what a multi-stage Dockerfile would look like, assuming the ansible-operator binary and python deps are present in some new image quay.io/operator-framework/ansible-controller-manager:latest?

tima commented 3 years ago

That naming is OK with me. I'm not sold on the multi-stage Dockerfile approach though. That seems inconsistent with the direction the Ansible community is heading with its efforts like ansible builder and execution environments.

openshift-bot commented 3 years ago

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 commented 3 years ago

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

estroz commented 3 years ago

/lifecycle frozen