Releases: cloudogu/k8s-dogu-operator
Releases · cloudogu/k8s-dogu-operator
v0.7.0
Added
- [#6] Installing generic kubernetes resources when installing a dogu. These resources need to be provided by the dogu image
at thek8s
folder in the root path (/k8s
):- There are no restriction for namespaced resources.
- The creation of cluster scoped resources is restricted and also their
deletion is not performed automatically as they could be used inside multiple namespaces.
Changed
- [#6] Update makefiles to version 6.0.2
v0.6.0
v0.5.0
v0.4.0
v0.3.1
v0.3.0
Added
- [#2] Annotation
k8s-dogu-operator.cloudogu.com/ces-services
to Dogu-Services
containing information of
related CES services. For more information see Annotations. - [#13] The automatic generation of service accounts
Changed
- [#11] Breaking Change ahead! The secret containing the dogu registry data was split and renamed from
dogu-registry-com
tok8s-dogu-operator-dogu-registry
andk8s-dogu-operator-docker-registry
.
It also received the registry endpoint as an additional literal besides username and password. Existing user
need to delete their old secret and create two new ones. The creation process is described
here and
here. - [#2] Update makefiles to version 5.0.0
v0.2.0
Added
- Add the opportunity to process custom dogu descriptors with configmaps #8
- Use status field of the dogu resource to identify its state #8
- Add functionality to remove dogus #4
- Restrict the dogu-operator with rbac resources to operate only in the configured namespace #4
Changed
- Ignore incoming dogu resources if their specs did not change #8
- this is likely to happen after status updates where the old and new dogu specs do not differ