Kopf

Latest version: v1.37.3

Safety actively analyzes 685670 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 15 of 18

0.19rc1

> _Originally released on 2019-07-09 13:11:00+00:00 ([link](https://github.com/zalando-incubator/kopf/releases/tag/0.19rc1))._

Improvements:

* Built-in resources (pods, namespaces) are now also supported. 110
* Handlers' INFO+ log messages are sent as Kubernetes events implicitly. 128

Internal changes:

* Switched the internal client from the official kubernetes-python top pykube-ng. 110
* Code coverage is measured. 72

0.18

> _Originally released on 2019-07-08 12:42:48+00:00 ([link](https://github.com/zalando-incubator/kopf/releases/tag/0.18))._

Improvements:

* Finalizer is not added if there are no deletion handlers. 118
* Deletion handlers can be optional to prevent adding finalizer. 118
* Script's dir is added to import paths to mimic Python's behaviour. 93 133
* `.status` is ignored in the last-handled state checks (except for fields used in field-handlers). 131
* `.metadata` is ignored in the last-handled state checks (except for labels & annotations). 131
* Operator freezes if the same-priority operator appears (previously, only warned). 114

Bugfixes:

* The peering self-record was not properly removed on exit. 114
* Restrict to `kubernetes<10.0.0` to keep Kopf runnable at all. 134

Internal changes:

* Examples can now have their own dedicated tests. 126

0.17.post1

> _Originally released on 2019-07-04 12:45:51+00:00 ([link](https://github.com/zalando-incubator/kopf/releases/tag/0.17.post1))._

Hotfix:

* Restrict to `kubernetes<10.0.0` to keep Kopf runnable at all.

See: 134 and kubernetes-client/python866

0.17

> _Originally released on 2019-07-03 08:23:43+00:00 ([link](https://github.com/zalando-incubator/kopf/releases/tag/0.17))._

Improvements:

* Performance improvements when handling hundreds of resources. 109

Internal changes:

* Internal (non-public) packages restructured — to deal with the growing complexity. 124
* `kopf.engines` extracted from `kopf.reactor` (peering & posting & logging).
* `kopf.utilities` extracted from `kopf.reactor` (reacting to k8s changes).
* `kopf.clients` is the new `kopf.k8s` (renamed).
* `kopf.clients.auth` extracted from `kopf.config` (only auth-related routines).
* `kopf.config` got the configuration constants from all over the code.
* New configuration added:
* Configurable timeouts and thread pool sizes.
* Configurable level of k8s-events posted; others are skipped.
* Everything has been made asynchronous:
* All internal K8s API wrappers/adapters are made async.
* All blocking operations (incl. API requests) moved to thread pools.
* All k8s-event posting is done via a queue with a background posting task. 125

0.16

> _Originally released on 2019-06-14 09:18:57+00:00 ([link](https://github.com/zalando-incubator/kopf/releases/tag/0.16))._

New features:

* Resource "resuming" handlers `kopf.on.resume` for threads/tasks. 105

Internal changes:

* Tests and docs for RBAC status codes for peering. 95
* Handlers are de-duplicated if registered twice and both do match the event/cause. 105
* The initial listing of objects is done separately from watching the objects, and is fed into the reactor differently (not `event['type']=="ADDED"`, but `event['type']==None`). The watching continues from the resource-version of the list, as it must be by design. 105

0.15

> _Originally released on 2019-06-13 16:14:01+00:00 ([link](https://github.com/zalando-incubator/kopf/releases/tag/0.15))._

New features:

* Silent spy-handlers `kopf.on.event` (currently only for custom resources). 86
* Labels can now be added recursively (e.g. to pod templates within jobs/deployments). 108

Improvements:

* Diffs are logged on update events. 104
* Handling is skipped if there are no handlers for the event/cause (and produces no fake logs/statuses). 103

Internal changes:

* Maintenance docs, RBAC fixes in the docs, typos fixed. 83 89 102
* Few more tests. 90 91

*The release is done as a rollback point from 0.16 if the resume-handlers introduce breaking changes (they shouldn't).*

Page 15 of 18

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.