wazuh/wazuh-kubernetes

Update Docker Image Version in Repository to Latest Available

Closed this issue · 2 comments

imusabkhan commented

I am currently attempting to install Wazuh using the latest wazuh-kubernetes repository 4.8.1. During the installation process, I encountered an issue with the Docker image version specified in the repository. The repository references Docker image version "5.0.0", but this version is not available on Docker Hub.

File: wazuh-kubernetes/wazuh/indexer_stack/wazuh-dashboard/dashboard-deploy.yaml
Container Image: wazuh/wazuh-dashboard:5.0.0
Line: 35

File: wazuh-kubernetes/wazuh/indexer_stack/wazuh-indexer/cluster/indexer-sts.yaml
Container Image: wazuh/wazuh-indexer:5.0.0
Line: 62

File: wazuh-kubernetes/wazuh/wazuh_managers/wazuh-master-sts.yaml
Container Image: wazuh/wazuh-manager:5.0.0
Line: 44

File: wazuh-kubernetes/wazuh/wazuh_managers/wazuh-worker-sts.yaml
Container Image: wazuh/wazuh-manager:5.0.0
Line: 47

Expected Behavior:
The repository should reference a Docker image version that is available on Docker Hub.

Actual Behavior:
The repository references Docker image version "5.0.0", which is not available on Docker Hub.

Reference:
Wazuh-Indexer
Wazuh-Dashboard
Wazuh-Manager

1- Wazuh-Manager-2 2- Docker-images 1- Wazuh-Dashboard 1- Wazuh-Indexer-1 3- DockerHub-1 3- DockerHub-3 3- DockerHub-2
crlsgms commented

If you had pulled the repo from the instructions, it will fetch the generic / master branch which the tags are with 5.0.0 that are not available yet, suggestion is to get on the release link and get the zip from there - v4.8.1

another way to have more control, or if you use a local registry is to add on your overlays kustomization.yml file all used images and tailor to your desired version, for example on mine using harbor registry:

images:
  - name: wazuh/wazuh-dashboard:4.8.0
    newName: harbor.local:30003/wazuh-proxy/wazuh/wazuh-dashboard
    newTag: 4.8.0
  - name: wazuh/wazuh-indexer:4.8.0
    newName: harbor.local:30003/wazuh-proxy/wazuh/wazuh-indexer
    newTag: 4.8.0
  - name: wazuh/wazuh-manager:4.8.0
    newName: harbor.local:30003/wazuh-proxy/wazuh/wazuh-manager
    newTag: 4.8.0
  - name: busybox
    newName: harbor.local:30003/wazuh-proxy/busybox
    newTag: latest
  - name: alpine
    newName: harbor.local:30003/wazuh-proxy/alpine
    newTag: latest
davidcr01 commented

Hello.

The issue you encountered is related to our versioning and release system. In our repositories, the master or the main branch contains the latest development code (n this case, the 5.0.0 version). This version is currently being developed so the Docker images are not built.

If you want to deploy the latest Wazuh version, I suggest you to check out the "Releases" part of the repository:
image.

There, you can check which is the latest version. This is also documented in our official documentation.

Then, once you get the latest version of Wazuh (or the version you want to deploy), change the branch of your local repository (assuming that the repository is cloned in your machine) with the git checkout command. For example, if you want to deploy the Wazuh v4.8.2 version, use the git checkout v4.8.2 command and you will move to the v4.8.2 tag, deploying the correct version.

Hope it helps. Regards.

  • 👍1