fix(openebs): update openebs version to 2.3.0

[akhilerm]

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

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

[akhilerm]

A few queries/thoughts I have:

• images in the kubesphere registry need to be updated to point to the latest version
• openebs images are now available as multiarch images, so pushing as multiarch into kubesphere repo will be better.
• Only openebs localpv hostpath storage class seems to be used in kubesphere. In that case, node-disk-manager and node-disk-operator are not required. (I have not updated this in the PR. Need to discuss on it)

[akhilerm]

/assign @Forest-L

[pixiake]

These images has been pushed to the kubesphere repo.

[stoneshi-yunify]

@akhilerm thanks for submitting this PR. You're correct, currently kubesphere only needs openebs localpv hostpath function, it is the easiest way to provision a pv so that kubesphere can be setup and launched very quickly, ndm and ndm operator seems not needed, can you remove them from kubekey within this PR?

We're also considering adding the full pack of openebs as a addon into the kubekey addon system so that user can install the full openebs and enjoy the complete features. You're also very welcome to contributing this part of code if you'd like.

Thanks very much!

[akhilerm]

@pixiake . Thank you. I have one concern on the image digest. The sha256 of images in kubesphere seems to be different from the upstream images available in openebs repo. Any idea why it happened.?

@stoneshi-yunify I have removed NDM components from the PR. Only the localPV provisioner is now installed. We may need to check if this breaks any existing systems / backward compatibility.

Having the full openebs pack would be great. Let me check on the add-on system in kubekey to see how it works.

[pixiake]

@akhilerm
I just checked the images‘ sha256，but found no difference.

quay.io/openebs/linux-utils:2.3.0
https://quay.io/repository/openebs/linux-utils/manifest/sha256:e8dd3cdec15de7c7d7bf39681ac55d34e5297c26200cbe4463a1eca858ed4a4f
quay.io/openebs/linux-utils-arm64:2.3.0
https://quay.io/repository/openebs/linux-utils-arm64/manifest/sha256:cf2cdadb4c2a61f20524c95402f70162cceed0e6a8553ada48fafc25703c72e2
kubesphere/linux-utils:2.3.0
amd64:
https://hub.docker.com/layers/126959961/kubesphere/linux-utils/2.3.0/images/sha256-e8dd3cdec15de7c7d7bf39681ac55d34e5297c26200cbe4463a1eca858ed4a4f
arm64:
https://hub.docker.com/layers/126959961/kubesphere/linux-utils/2.3.0/images/sha256-cf2cdadb4c2a61f20524c95402f70162cceed0e6a8553ada48fafc25703c72e2

quay.io/openebs/provisioner-localpv:2.3.0
https://quay.io/repository/openebs/provisioner-localpv/manifest/sha256:8440997ae1997584b58bc463377687e80f42a72c316eb608785da5d4ae8af1a9
quay.io/openebs/provisioner-localpv-arm64:2.3.0
https://quay.io/repository/openebs/provisioner-localpv-arm64/manifest/sha256:f7d88fd208be2c87bc0269ae9826cd5b3934282886774586f08030718fac237c
kubesphere/provisioner-localpv:2.3.0
amd64:
https://hub.docker.com/layers/126959609/kubesphere/provisioner-localpv/2.3.0/images/sha256-8440997ae1997584b58bc463377687e80f42a72c316eb608785da5d4ae8af1a9
arm64:
https://hub.docker.com/layers/126959609/kubesphere/provisioner-localpv/2.3.0/images/sha256-f7d88fd208be2c87bc0269ae9826cd5b3934282886774586f08030718fac237c

[akhilerm]

@pixiake. Ok got it . kubesphere is fetching the images from quay.

So, with the latest version of openebs , we are building multiarch images and pushing to docker hub. The image-{arch} are maintained in quay so as to not to break anyone during the transition to multiarch images. (NOTE: We still havent found out a reliable way to push multiarch image to different registries from our CI. So we default to dockerhub for now.)

can you check this multiarch image in docker hub. It has support for amd64, arm64, arm/v7 and power PC.

[pixiake]

@akhilerm
That's great, since multiarch images are already supported in docker hub, I think we can just use openebs repo.

[akhilerm]

@akhilerm
That's great, since multiarch images are already supported in docker hub, I think we can just use openebs repo.

I think the registry is specified as part of the ClusterSpec, so I dont think changes are needed in this PR for moving to openebs repo.

[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

[pixiake]

@akhilerm Thanks for the contribution.

[pixiake]

/lgtm