chore(openebs): update openebs version to 2.9.0

[akhilerm]

• update openebs image version to 2.9.0
• use latest operator yaml

Signed-off-by: Akhil Mohan akhil.mohan@mayadata.io

[akhilerm]

@pixiake PTAL.

[pixiake]

@akhilerm Thanks for the contribution！

[pixiake]

/lgtm

[akhilerm]

@pixiake How can the image repository/registry be configured here?

[pixiake]

@akhilerm
You can add spec.registry.privateRegistry to the configuration file.
If the registry is configured，kk will use it to generate the image's name.

For example:
registry: dockerhub.kubekey.local
image's name: dockerhub.kubekey.local/openebs/linux-utils:2.9.0

[pixiake]

/approve

[ks-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akhilerm, pixiake

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [pixiake]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[akhilerm]

For example:
registry: dockerhub.kubekey.local
image's name: dockerhub.kubekey.local/openebs/linux-utils:2.9.0

So the images are always fetched from openebs docker hub or the kubesphere docker hub?

[pixiake]

For example:
registry: dockerhub.kubekey.local
image's name: dockerhub.kubekey.local/openebs/linux-utils:2.9.0

So the images are always fetched from openebs docker hub or the kubesphere docker hub?

Yes，if there is no image repository is configured, always pull images from openebs docker hub. The namespace of the image is unchanged.