-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Operator SDK 1.0 Meta-issue #3327
Labels
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
Comments
estroz
added
the
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
label
Jul 1, 2020
For anyone interested, this PR adds a migration tool to migrate a legacy project to a new one: #2851. |
8 tasks
5 tasks
2 tasks
This was referenced Jul 20, 2020
Merged
Merged
This was referenced Jul 26, 2020
camilamacedo86
added a commit
that referenced
this issue
Jul 27, 2020
**Description of the change:** - Add info why use the domain ( request made by users ) - Add info regards the metrics changes - small improvements **Motivation for the change:** #3327
@joelanford Can I get the ETA of the operator SDK V1.0? Thanks! |
@xiangjingli Current plan is mid-next week, barring any unforeseen issues that arise between now and then. |
1.0 was released a few weeks ago. Closing this out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
The Operator SDK maintainers and community members have been hard at work adding new features to improve integration with the Operator Lifecycle Manager and to unify project structures with Kubebuilder.
Many of these features are already on
master
, but some are still outstanding. The purpose of this issue is to communicate with the community about what the proposed 1.0 feature set is, and to document what's in, what's out, and what major changes we plan to make for existing projects.Support for legacy project layouts (scaffolded with the
new
subcommand) will be removed for 1.0. The latest pre-1.0 release will receive patch updates to give users time to migrate to the new project structure. No new features will be backported from 1.0 to the latest pre-1.0 release.1.0.0 GA
operator-sdk cleanup
command (operator-sdk cleanup: remove packagemanifests, add generic command #3644)1.0.0-alpha.2
--operator-name
#3530)internal/log
(cmd/helm|ansible-operator: add cobra subcommands #3596)operator-framework/api
and removepkg/apis
(pkg/apis: add scorecard v1alpha3 API api#55) (scorecard: use api repo v1alpha3 API, remove existing #3622)run packagemanifests
flags--include
and--olm-namespace
flags (<run|cleanup> packagemanifests: remove--include-paths
, change--operator-version
to--version
#3599, <run|cleanup> packagemanifests: remove--olm-namespace
, change--operator-namespace
to--namespace
#3601)--operator-version
to--version
(<run|cleanup> packagemanifests: remove--include-paths
, change--operator-version
to--version
#3599)--operator-namespace
to--namespace
(<run|cleanup> packagemanifests: remove--olm-namespace
, change--operator-namespace
to--namespace
#3601)What's added in
v1.0.0
operator-sdk generate kustomize manifests
operator-sdk generate bundle
operator-sdk generate packagemanifests
operator-sdk <run|cleanup> packagemanifests
operator-sdk scorecard
will be updated with the new scorecard implementation, currently underoperator-sdk alpha scorecard
(Scorecard move alpha #3444)operator-sdk scorecard
will support both sequential and parallel stages (internal/scorecard/alpha: add parallelism support #3434)--max-workers
to--max-concurrent-reconciles
(ansible/helm: Rename max-workers to max-concurrent-reconciles #3452, fix: remove max-workers flag for ansible #3456)WORKER_%s_%s
envvar toMAX_CONCURRENT_RECONCILES_%s_%s
(ansible: rename cmd line flag and add global variable #3435)pkg/log/zap
tointernal/log/zap
(move zap flags internally #3525)leader.Become
in operator-lib (Leader remove runlocal operator-lib#7)handler/enqueue_annotation.go
with changes from ✨ add EnqueueRequestForAnnotation enqueues Requests based on the presence of an annotation to watch resources kubernetes-sigs/controller-runtime#892 (Update hander/enqueue_annotation.go operator-lib#2)pkg/handler/enqueue_annotation.go
from operator-sdk; have ansible to useoperator-framework/operator-lib/handler
instead (Remove EnqueueRequestForAnnotation handler from SDK #3506)pkg/handler/instrumented
from operator-sdk; have ansible/helm useoperator-framework/operator-lib/handler
instead (replace instrumented handler with the one from operator-lib #3523)GenerationChangedPredicate
frompredicate
. Movedpkg/predicate
topkg/ansible/predicate
(Move pkg/predicate closer to where it is used. #3491pkg/predicate: move predicates elsewhere and remove #3532).yml
changelog fragments (allow fragments to end in either .yml or .yaml #3493)InstrumentedEnqueueRequestForObject
to operator-lib (Added new handler for metrics operator-lib#8)go.mod
requires to use tagged versions of operator-lib and controller-runtime (bump operator-lib to v0.1.0 #3616)operator-sdk
repository has no exported public Go APIs.What's removed in
v1.0.0
operator-sdk exec-entrypoint
([ansible/helm] remove operator-sdk binary from ansible/helm base images #3331)operator-sdk build
(cmd/operator-sdk: removebuild
subcommand #3566)operator-sdk add api
for Go operators (Remove legacy CLI, code, and scaffold templates #3385)operator-sdk add controller
(Remove legacy CLI, code, and scaffold templates #3385)operator-sdk add crd
for Go operators (*: remove theadd crd
subcommand and related utilities #3547)operator-sdk migrate
(Remove legacy CLI, code, and scaffold templates #3385)operator-sdk print-deps
(Remove legacy CLI, code, and scaffold templates #3385)operator-sdk generate k8s
(Remove legacy CLI, code, and scaffold templates #3385)operator-sdk generate crds
(Remove legacy CLI, code, and scaffold templates #3385)operator-sdk test
subcommand and e2e framework are being removed. Users should migrate toenvtest
. (*: removetest
subcommand,pkg/test
, and internal e2e tests for legacy projects #3409)operator-sdk run local
. To continue supporting running helm and ansible operators locally, we will release these binaries so that upcomingmake run
targets for those operator types can download and run the operator binaries locally. (cmd/operator-sdk/run: remove legacy run subcommand #3406)operator-sdk cleanup
for legacy projects. (cmd/operator-sdk/run: remove legacy run subcommand #3406)run packagemanifests
support (cmd/operator-sdk/run: remove legacy run subcommand #3406)generate csv
(Remove legacy generate and bundle commands #3414)generate bundle
(Remove legacy generate and bundle commands #3414)generate packagemanifests
(Remove legacy generate and bundle commands #3414)operator-sdk bundle <create/validate>
is removed. (Remove legacy generate and bundle commands #3414)test/test-framework
sample project that is used for legacy tests (test/test-framework: remove, and update/remove references and dependent tests #3424)operator-sdk [new|add api]
CLI for Helm operators (removal: helm legacy scaffold #3343)pkg/metrics
andpkg/kube-metrics
WATCH_NAMESPACE
andPOD_NAME
environment variables from manager template (internal/plugins/ansible: manager scaffolding updates for --metrics-addr and envvars #3570)Checklist for 1.0.0-alpha1 release
controller-tools/pkg/markers
#2792)operator-sdk [new|add api]
CLI for Ansible operators (Remove operator-sdk new|add api commands and ansible scaffolding. #3531)operator-sdk scorecard
config file is a componentconfig (scorecard: make config a componentconfig, scaffold config kustomization oninit
#3490)init
#3490)--project-name
and useConfig.ProjectName
in scaffold #3438)pkg/helm
tointernal/helm
(Move pkg/helm to internal/helm #3537)pkg/ansible
tointernal/ansible
(*: move pkg/ansible to internal/ansible #3560)manager.yaml
(internal/plugins/ansible: manager scaffolding updates for --metrics-addr and envvars #3570)The text was updated successfully, but these errors were encountered: