Dear LINSTOR on Kubernetes users,
We are pleased to announce version v0.5.0 of linstor-operator, our
all-in-one
package for gettings started with LINSTOR on Kubernetes. This is the
first
release to feature on this mailing list, so if you are unfamiliar with
the
project, we recommend you check out the user guide section on
Kubernetes[1].
For those already following the project, this new release focuses on
providing
an all-in-one deployment for all LINSTOR features, ready for
Kubernetes. To this
end, various components that required manual installation can now be
configured
by linstor-operator. You can find a detailed list of changes below.
Upstream code can be found here[2].
Best regards,
Moritz
Changelog:
* Kubernetes Volume Expansion:
linstor-operator now installs the required controllers for this
feature.
This feature requires support from Kubernetes, enabled by default
since v1.16
See [3]
* Kubernetes Volume Snapshots:
Snapshots can be created via Kubernetes resources, and restored to
new PV.
linstor-operator now installs the required controllers for this
feature.
This feature requires support from Kubernetes, enabled by default
since v1.17
See [4] and [5]
* Stork:
LINSTOR can integrate with the Stork[6] project to aid Kubernetes in
scheduling pods near their volumes. linstor-operator now installs a
new scheduler that integrates with LINSTOR.
See [7]
* new option for `drbdKernelModuleInjectionMode`: `DepsOnly`:
Previously, kernel module loading was an "all-or-nothing" decision.
`Compile`/`ShippedModules` would try to load all modules, `None`
would not
load any modules at all. `DepsOnly` tries to load all modules, but
only those
already installed on the host machine.
See [8]
* new etcd deployment:
linstor-operator comes packaged with an `etcd` deployment to get
started.
The previous deployment operator had difficulties recovering from
failed
nodes. The new version is more robust in case of temporary loss of
nodes.
Some important keys for the `etcd` helm chart have changed:
* `statefulset.replicaCount` -> `replicas`
* `persistence.enabled` -> `persistentVolume.enabled`
* `persistence.size` -> `persistentVolume.storage`
* `?uth.rbac` was removed: use tls certificates.
* `auth.peer.useAutoTLS` was removed
* `envVarsConfigMap` was removed
* When using etcd with TLS enabled:
* For peer communication, peers need valid certificates for
`*.<release-name>-etcd` (was
`.<release-name>>-etcd-headless.<namespace>.svc.cluster.local`)
* For client communication, servers need valid certificates for
`*.<release-name>-etcd` (was
`.<release-name>>-etcd.<namespace>.svc.cluster.local`)
[1]:
https://www.linbit.com/drbd-user-guide/linstor-guide-1_0-en/#ch-kubernetes
[2]: https://github.com/piraeusdatastore/piraeus-operator
[3]:
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#csi-volume-expansion
[4]:
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#volume-snapshot-and-restore-volume-from-snapshot-support
[5]:
https://www.linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-snapshots
[6]: https://github.com/libopenstorage/stork
[7]:
https://www.linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-stork
[8]:
https://www.linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-deploy
_______________________________________________
drbd-announce mailing list
drbd-announce@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-announce
We are pleased to announce version v0.5.0 of linstor-operator, our
all-in-one
package for gettings started with LINSTOR on Kubernetes. This is the
first
release to feature on this mailing list, so if you are unfamiliar with
the
project, we recommend you check out the user guide section on
Kubernetes[1].
For those already following the project, this new release focuses on
providing
an all-in-one deployment for all LINSTOR features, ready for
Kubernetes. To this
end, various components that required manual installation can now be
configured
by linstor-operator. You can find a detailed list of changes below.
Upstream code can be found here[2].
Best regards,
Moritz
Changelog:
* Kubernetes Volume Expansion:
linstor-operator now installs the required controllers for this
feature.
This feature requires support from Kubernetes, enabled by default
since v1.16
See [3]
* Kubernetes Volume Snapshots:
Snapshots can be created via Kubernetes resources, and restored to
new PV.
linstor-operator now installs the required controllers for this
feature.
This feature requires support from Kubernetes, enabled by default
since v1.17
See [4] and [5]
* Stork:
LINSTOR can integrate with the Stork[6] project to aid Kubernetes in
scheduling pods near their volumes. linstor-operator now installs a
new scheduler that integrates with LINSTOR.
See [7]
* new option for `drbdKernelModuleInjectionMode`: `DepsOnly`:
Previously, kernel module loading was an "all-or-nothing" decision.
`Compile`/`ShippedModules` would try to load all modules, `None`
would not
load any modules at all. `DepsOnly` tries to load all modules, but
only those
already installed on the host machine.
See [8]
* new etcd deployment:
linstor-operator comes packaged with an `etcd` deployment to get
started.
The previous deployment operator had difficulties recovering from
failed
nodes. The new version is more robust in case of temporary loss of
nodes.
Some important keys for the `etcd` helm chart have changed:
* `statefulset.replicaCount` -> `replicas`
* `persistence.enabled` -> `persistentVolume.enabled`
* `persistence.size` -> `persistentVolume.storage`
* `?uth.rbac` was removed: use tls certificates.
* `auth.peer.useAutoTLS` was removed
* `envVarsConfigMap` was removed
* When using etcd with TLS enabled:
* For peer communication, peers need valid certificates for
`*.<release-name>-etcd` (was
`.<release-name>>-etcd-headless.<namespace>.svc.cluster.local`)
* For client communication, servers need valid certificates for
`*.<release-name>-etcd` (was
`.<release-name>>-etcd.<namespace>.svc.cluster.local`)
[1]:
https://www.linbit.com/drbd-user-guide/linstor-guide-1_0-en/#ch-kubernetes
[2]: https://github.com/piraeusdatastore/piraeus-operator
[3]:
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#csi-volume-expansion
[4]:
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#volume-snapshot-and-restore-volume-from-snapshot-support
[5]:
https://www.linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-snapshots
[6]: https://github.com/libopenstorage/stork
[7]:
https://www.linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-stork
[8]:
https://www.linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-deploy
_______________________________________________
drbd-announce mailing list
drbd-announce@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-announce